Nokia Solutions and Networks Oy

Nokia Technologies Oy

Hooman Bidgoli

Jayant Kotalwar

Filip Martin

Andrew W Stone

Michael Long

Georges Chung Kam Chung

A controller includes a transceiver to establish a first session with a route reflector and monitor advertisements received by the route reflector from nodes in a network via second sessions established between the nodes and the route reflector. The controller also includes a processor to generate forwarding instructions for the nodes based on the advertisements. The forwarding instructions indicate one or more routes from a root node to one or more leaf nodes of a service. The transceiver provides the forwarding instructions to the root node. In some cases, the first session is established according to the border gateway protocol (BGP) and the one or more second sessions are established according to the BGP. The controller determines that the one or more leaf nodes are registered for one or more virtual private network (VPN) services based on the advertisements.

Configuring routes based on passive monitoring of advertisements to route reflector

Various example embodiments for supporting multicast are presented. Various example embodiments for supporting multicast are configured to support multicast, on a multicast tree for a multicast group, based on use of penultimate hop popping (PHP) on the multicast tree. Various example embodiments for supporting multicast are configured to support multicast, on a multicast tree for a multicast group, based on use of PHP on the multicast tree where the multicast tree is Point-to-Multipoint (P2MP) Multiprotocol Label Switching (MPLS) tree that is formed based on a TREE-SID multicast solution (although it will be appreciated that PHP may be applied on other types of multicast trees (e.g., other than P2MP MPLS multicast trees), on multicast trees formed based on other multicast solutions (e.g., other than TREE-SID), or the like, as well as various combinations thereof).

Multicast based on penultimate hop popping

Various example embodiments for supporting candidate path selection in a communication system are presented. The support for candidate path selection may be based on candidate path preference information of the candidate paths where the candidate path preference information of the candidate paths may be configured for use by network devices in selecting between the candidate paths. The support for candidate path selection based on candidate path preference information of the candidate paths may be provided within the context of candidate path selection which may include failover switching. The support for candidate path selection based on candidate path preference information may be based on support for distribution of the candidate path preference information of the candidate paths to network devices and use of the candidate path preference information of the candidate paths by the network devices to support selection of the candidate paths.

Supporting candidate path selection

Various example embodiments for supporting packet routing in a communication system may be configured to, in a communication network, support use of primary routing paths for routing traffic in the communication network and use of controller provided protection paths configured to protect the primary paths based on rerouting of traffic around failures in the communication network. Various example embodiments for supporting packet routing in a communication system may be configured to support controller provided protection paths in a communication network based on use of path control capabilities in which a network controller computes paths for a network and configures the paths in the network based on configuration of the paths on nodes of the network and based on routing capabilities in which the nodes use the routing paths for routing of traffic (e.g., via primary paths) and rerouting of traffic (e.g., via controller provided protection paths).

Controller provided protection paths

The present disclosure generally discloses a multicast capability configured to support multicast that is based on use of Bit Indexed Explicit Replication (BIER). The multicast capability may be configured to support deployment of BIER into a network in a manner that continues to support use of Protocol Independent Multicast (PIM) for multicast control within the network. The multicast capability may be configured to support deployment of BIER, into a network including an Interior Gateway Protocol (IGP) area, using a BIER domain that is commensurate with the IGP area or that is only a portion of the IGP area. The multicast capability may be configured to support deployment of BIER into a network in a manner supporting stitching of traditional PIM access networks via a BIER core network.

Multicast based on bit indexed explicit replication

Various example embodiments for supporting generation of addresses for network entities in communication systems are presented. Various example embodiments for supporting generation of addresses for network entities may be configured to support generation of a new address for a network entity based on an existing address of the network entity. Various example embodiments for supporting generation of addresses for network entities may be configured to support generation of a new address for a network entity based on manipulation of at least a portion of an existing address of the network entity. Various example embodiments for supporting generation of addresses for network entities may be configured to support generation of a transport layer address (e.g., an Internet Protocol (IP) address or the like) for a network entity based on a data link layer address (e.g., a Media Access Control (MAC) address or the like) of the network entity.

Address generation

Various example embodiments relate generally to supporting Multiprotocol Label Switching (MPLS)-based multicast over a Bit Index Explicit Replication (BIER) domain. Various example embodiments for supporting MPLS-based multicast over a BIER domain may be configured to support MPLS point-to-multipoint (P2MP) label switched paths (LSPs) over a BIER domain. Various example embodiments for supporting MPLS-based multicast over a BIER domain may be configured to support establishment and transport of P2MP LSPs over a BIER domain (e.g., signaling MPLS via the BIER domain, stitching the MPLS datapath to the BIER domain based on identification of P2MP LSPs within the BIER domain, and so forth).

Supporting multicast over a network domain

Various example embodiments for supporting multicast in communication systems are presented. In at least some example embodiments, supporting multicast in communication systems may include supporting use of multicast domain information of a penultimate hop router of the multicast domain by an egress leaf router associated with the multicast domain for multicast service signaling to a root router of the multicast domain. In at least some example embodiments, in which the multicast domain is based on Bit Index Explicit Replication (BIER), supporting multicast in communication systems may include supporting use of BIER domain information (e.g., a BIER Forwarding Router Identifier (BFR-ID) or the like) of a PH BIER router by an egress leaf router associated with the BIER domain for multicast service signaling to a root BIER router of the BIER domain.

Multicast support

A border router includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code is configured to, with the at least one processor, cause the border router to: identify, in response to receiving a label mapping message from a network node, a backup border router as a hop in a backup path between a leaf node and a root node in a multicast network including an autonomous system, the label mapping message including a type-length-value; determine whether the backup border router is an originating border router having generated the label mapping message based on the type-length-value; and suppress mapping of the hop in the backup path in response to determining that the backup border router is the originating border router.

Growing community of inventors

Ottawa, Canada

Hooman Bidgoli