Patent application number | Description | Published |
20080310417 | DIFFERENTIAL FORWARDING IN ADDRESS-BASED CARRIER NETWORKS - The invention relates to enabling differential forwarding in address-based carrier networks such as Ethernet networks. There is described a method of and connection controller for establishing connections ( | 12-18-2008 |
20090059799 | SCALING OAM FOR POINT-TO-POINT TRUNKING - A shared (proxy) OAM session is performed in a packet-based network on behalf of a plurality of connections. First and second connections are each routed between respective nodes of the network for carrying data traffic. The second connection shares a portion of the routing of the first connection. The shared OAM session is performed along a path which is co-routed with at least part of the shared portion of the routing of the first connection and the second connection. Failure notification signalling is propagated to an endpoint node of each of the first and second connections when the shared OAM session indicates a failure has occurred. The use of a shared OAM session reduces processing at nodes and reduces OAM traffic. Each connection can be a trunk, such as a PBT/PBB-TE trunk, or a service carried within a trunk. | 03-05-2009 |
20090161669 | Evolution of Ethernet Networks - An Ethernet network comprises nodes which support a plurality of different forwarding modes. A range of VLAN Identifiers (VIDs) are allocated to each of the forwarding modes. Connections are configured between a source node and a destination node of the network using different forwarding modes. Packets carrying data traffic are sent to the destination node by selectively setting a VID in a packet to a first value, to transfer a packet via a first connection and a first forwarding mode, and a second value to transfer a packet via the second connection and the second forwarding mode. Packets received from both of the connections and sent on to an end-user. VLAN Identifiers can be allocated to different releases of functionality at nodes (e.g. software releases) such that packets are forwarded via a set of nodes supporting a first release, or via a set of nodes supporting a second release. It is possible to provide a controlled and disruption-free network evolution. | 06-25-2009 |
20090168663 | Reducing Configuration of OAM Signalling Data - OAM data is automatically configured by each node of an Ethernet network. The OAM data is required to support an OAM signalling session associated with a connection for carrying data traffic between nodes. The OAM data can be derived from data already associated with all endpoints of the connection. The node can derive the OAM data autonomously. A node which is an endpoint of an OAM signalling session automatically derives an identifier for the first endpoint. The first identifier can be autonomously derived by the node and other signalling content, such as source MAC address, is used to differentiate OAM signalling messages. Alternatively, a node can automatically configure the first identifier on the basis of information stored locally at the node and signalling with a second endpoint. The OAM data can be IEEE 802.1ag or ITU Y.1731 data. | 07-02-2009 |
20100189015 | Planning Routes and Allocating Identifiers to Routes in a Managed Frame-Forwarding Network - A method is provided of planning routes and allocating route identifiers in a managed frame-forwarding network. The network comprises a plurality of nodes interconnected by links, with each node being arranged to forward data frames according to a combination of an identifier and a network address carried by a received data frame and forwarding instructions stored at the node. A first step of the method identifies a sub-set of nodes which are core nodes of the network. The remaining nodes are termed outlying nodes. A spanning tree is then built off each of the identified core nodes, with the spanning tree stopping one link short of any other core node. Each spanning tree defines a loop-free path between a core node at the root of the spanning tree and a set of outlying nodes. Connections are planned between roots of the spanning trees and a different identifier is allocated to each planned connection between a pair of spanning trees. | 07-29-2010 |
20130070586 | Scaling OAM for Point-to-Point Trunking - A shared (proxy) OAM session is performed in a packet-based network on behalf of a plurality of connections. First and second connections are each routed between respective nodes of the network for carrying data traffic. The second connection shares a portion of the routing of the first connection. The shared OAM session is performed along a path which is co-routed with at least part of the shared portion of the routing of the first connection and the second connection. Failure notification signalling is propagated to an endpoint node of each of the first and second connections when the shared OAM session indicates a failure has occurred. The use of a shared OAM session reduces processing at nodes and reduces OAM traffic. Each connection can be a trunk, such as a PBT/PBB-TE trunk, or a service carried within a trunk. | 03-21-2013 |
20130100801 | PROVIDER BACKBONE BRIDGING - PROVIDER BACKBONE TRANSPORT INTERNETWORKING - An Ethernet virtual switched sub-network (VSS) is implemented as a virtual hub and spoke architecture overlaid on hub and spoke connectivity built of a combination of Provider Backbone Transport (spokes) and a provider backbone bridged sub-network (hub). Multiple VSS instances are multiplexed over top of the PBT/PBB infrastructure. A loop free resilient Ethernet carrier network is provided by interconnecting Provider Edge nodes through access sub-networks to Provider Tandems to form Provider Backbone Transports spokes with a distributed switch architecture of the Provider Backbone Bridged hub sub-network. Provider Backbone transport protection groups may be formed from the Provider Edge to diversely homed Provider Tandems by defining working and protection trunks through the access sub-network. The Provider Backbone Transport trunks are Media Access Control (MAC) addressable by the associated Provider Edge address or by a unique address associated with the protection group in the Provider Backbone Bridged network domain. | 04-25-2013 |
20150341709 | METHODS AND APPARATUS FOR DETERMINING A PATH IN A COMMUNICATIONS NETWORK - A method for determining a path in an optical network, implemented by one or more controllers associated with a control layer, includes receiving a path request specifying start and end points, an associated bandwidth, and a longevity parameter providing an anticipated length during which the path is required; determining a route in the optical network through a routing algorithm executed by the controller, wherein the routing algorithm utilizes the start and end points, the associated bandwidth, and the longevity parameter to determine the path; and provisioning the path through a plurality of switches along the route. | 11-26-2015 |