A network node device and method of determining a communication route to one or more other network nodes through a network. The method includes sending current routing information to a network management server (NMS), and receiving new or supplemental routing information from the NMS, this supplemental routing information determined by the NMS based on the current routing information of the network node and the other network node(s). The supplemental routing information may include lateral route information identifying designated routing nodes that form lateral band(s) of nodes that span the network. Each lateral band may include gate node(s) as entrances/exits to the lateral band. The method further includes determining, based on the supplemental routing information, a route to one or more of the other network nodes, which may include an optimal path and/or alternate path(s) from the network node to one or more of the other network nodes.

In one aspect, a computerized method of an application routing service includes the step of using a deep-packet inspection (DPI) technique on a first network flow to identify an applications The method includes the step of storing an Internet-protocol (IP) address and a port number used by the application and an identity of the application in a databases The method includes the step of detecting a second network flow. The method includes the step of identifying the IP address and the port number of the application in the second network flow. The method includes the step of looking up the IP address and the port number in the database. The method includes the step of identifying the application based on the IP address and the port number.

In one aspect, a computerized method of an application routing service includes the step of using a deep-packet inspection (DPI) technique on a first network flow to identify an applications The method includes the step of storing an Internet-protocol (IP) address and a port number used by the application and an identity of the application in a databases The method includes the step of detecting a second network flow. The method includes the step of identifying the IP address and the port number of the application in the second network flow. The method includes the step of looking up the IP address and the port number in the database. The method includes the step of identifying the application based on the IP address and the port number.

A method for establishing a segment routing (SR) tunnel based on an Internet Protocol version 6 (IPv6) data plane using a Path Computation Element Communication Protocol (PCEP) includes generating, by a path computation element (PCE), a first PCEP message, wherein the first PCEP message comprises indicating information and segment identifier (SID), and wherein the indicating information indicates that the SID is an IPv6 prefix of a node in a tunnel; receiving, by a first path computation client (PCC), the first PCEP message from the PCE; and establishing, by the first PCC, a Segment Routing over IPv6 (SRv6) tunnel from the first PCC to a second PCC.

Embodiments provide functionality for dynamic handling of network slice priorities. In an embodiment, a slice priority manager receives, from a network services node, data indicating changes in network resources available for maintaining instantiated network slices in a communication network. Based on the received data, changes in the network services node's ability to maintain the instantiated network slices are identified and a communication service provider is notified of the change. To continue, slice priority data that indicates a preferred order of a portion of the network slices for allocating the network resources is received from the communication service provider. In turn, an indication of the slice priority data is forwarded to the network services node to update allocation of network resources for the slices.

Some embodiments provide a method that receives (i) definition of a group of virtual datacenters and (ii) addition of at least two virtual datacenters to the group. Each virtual datacenter is defined in a public cloud and includes a set of network management components and a set of network endpoints connected by a logical network that is managed by the network management components of the virtual datacenter. Based on the definition of the group, the method configures a gateway router to which each of the virtual datacenters of the group connect. The gateway router is for routing traffic between the virtual datacenters of the group. The method also configures, at each respective virtual datacenter, a respective router to route data traffic between the respective virtual datacenter and the other virtual datacenters to route traffic for the other virtual datacenters to the gateway router.

Some embodiments provide a method that receives (i) definition of a group of virtual datacenters and (ii) addition of at least two virtual datacenters to the group. Each virtual datacenter is defined in a public cloud and includes a set of network management components and a set of network endpoints connected by a logical network that is managed by the network management components of the virtual datacenter. Based on the definition of the group, the method configures a gateway router to which each of the virtual datacenters of the group connect. The gateway router is for routing traffic between the virtual datacenters of the group. The method also configures, at each respective virtual datacenter, a respective router to route data traffic between the respective virtual datacenter and the other virtual datacenters to route traffic for the other virtual datacenters to the gateway router.

A route calculation method, device, and system. The route calculation method includes: receiving, by a first device, a service request message, where the service request message is used to request the first device to determine a transmission path of a borne service requested by the service request message to be established; and determining, by the first device, a transmission path of the service based on the service request message and first bearing capability information, where the first bearing capability information is used to indicate an actual bearing capability of each link on the transmission path. According to the foregoing solution, the system can calculate a route and configure the service based on an actual service bearing capability of each link of a network.

A data transmission method, a node, and a system, the method including receiving, by a forwarding node, a data packet, where a label stack of the data packet comprises a path identifier (path-ID), where the path-ID is an identifier of a constrained path, and where the constrained path is a path that consists of at least two nodes arranged in a specific order, determining, by the forwarding node, that the forwarding node is a node on the constrained path, selecting, by the forwarding node, a target label/target address from a local available label block/address block according to the path-ID and according to a preset rule, where the label block/address block comprises at least one label/address, searching for, by the forwarding node, a corresponding target interface according to the target label/target address, and forwarding, by the forwarding node, the data packet through the target interface.

Disclosed is a system and method of providing a segment routing as a service application. The method includes receiving a configuration of an internet protocol environment. The configuration can be a layer 3 configuration of a single cloud environment or even across multiple cloud environments. The configuration defines routing, forwarding, and paths in the environment between different entities such as virtual machines. The method includes receiving a parameter associated with a workload of a tenant. The parameter can be a service level agreement (i.e., a best bandwidth available), a pathway requirement, a parameter associated with specific workload, and so forth. Based on the configuration and the parameter, the method includes generating tenant-defined layer 3 overlay segment routing rules that define how the workload of the tenant will route data in the internet protocol environment using segment routing.