Patent application number | Description | Published |
20090168647 | Interworking an Ethernet Ring Network and an Ethernet Network with Traffic Engineered Trunks - Interworking an Ethernet Ring network with an Ethernet network with traffic engineered trunks (PBT network) enables traffic engineered trunks to be dual homed to the Ethernet ring network to enable for protection switching between active and backup trunk paths in the PBT network. In one embodiment, the active path will terminate at a first bridge node on the Ethernet ring network and the backup path will terminate at a second bridge node on the Ethernet ring network. Trunk state information is exchanged between the bridge nodes to enable the bridge nodes to determine which of the active and backup paths should be used to forward data on the trunk. Upon a change in trunk state, a flush message is transmitted on the Ethernet ring network to enable the nodes on the Ethernet ring network to relearn the path to the new responsible bridge node. | 07-02-2009 |
20090168671 | Interworking an Ethernet Ring Network with a Spanning Tree Controlled Ethernet Network - To enable an Ethernet ring to be dual homed into a spanning tree protocol controlled Ethernet network, spanning tree control packets (Bridged Protocol Data Units or BPDUs) are transported as data frames over the Ethernet ring. This allows the Ethernet ring to appear as a single link to the spanning tree protocol so that the spanning tree can extend over the link. However, since the spanning tree does not have visibility as to the internal structure of the ring, the spanning tree cannot block links on the Ethernet ring network. Conversely, BPDUs from the Ethernet ring are not transmitted into the Ethernet domain that is implementing the spanning tree, so that the spanning tree is not affected by the control mechanism in place on the Ethernet ring network. | 07-02-2009 |
20090202239 | Service Management Channel for Managing an Optical Networking Service - An optical network and method for managing a service across an optical network over a dedicated circuit between first and second service termination points include generating a service performance report message (PRM) at each service termination point. Each service PRM has service-specific information related to a performance of the service as determined by the service termination point generating that service PRM. Each service PRM identifies the service to which the service-specific information in that service PRM pertains. Each service termination point transmits the service PRM generated by that service termination point across the optical network over the dedicated circuit to the other service termination point through a service management channel of an optical transport facility. Either of the first and second service termination points is accessed to evaluate an end-to-end performance of the service based on a comparison of the service PRM generated by the first service termination point with the service PRM generated by the second service termination point. | 08-13-2009 |
20100238813 | Q-in-Q Ethernet rings - A resilient virtual Ethernet ring has nodes interconnected by working and protection paths. Each node has a set of VLAN IDs (VIDs) for tagging traffic entering the ring by identifying the ingress node and whether the traffic is on the working or protection path. MAC addresses are learned in one direction around the ring. A port aliasing module records in a forwarding table a port direction opposite to a learned port direction. Each node can also cross-connect working and protection paths. If a span fails, the two nodes immediately on either side of the failure are cross-connected to fold the ring working-path traffic is cross-connected onto the protection path at the first of the two nodes and is then cross-connected back onto the working path at the second of the two nodes so that traffic always ingresses and egresses the ring from the working path. | 09-23-2010 |
20110164502 | ETHERNET OAM PERFORMANCE MANAGEMENT - Maintenance entities may be defined between customer and provider flow points to allow performance management to take place on an Ethernet network. The maintenance entities may be defined for access link, intra-domain, and inter-domain, and may be defined on a link or service basis. The maintenance entities may be used to monitor performance within a network or across networks, and may be used to monitor various performance parameters, such as frame loss, frame delay, frame delay variation, availability, errored frame seconds, service status, frame throughput, the number of frames transmitted, received or dropped, the status of a loopback interface, the amount of time a service has been unavailable, and many other parameters. Several management mechanisms may be used, and the measurements may be collected using a solicited collection method, in which a response is required and collected, or an unsolicited collection method in which a response is not required. | 07-07-2011 |
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 |
20140086064 | ETHERNET OAM PERFORMANCE MANAGEMENT - Maintenance entities may be defined between customer and provider flow points to allow performance management to take place on an Ethernet network. The maintenance entities may be defined for access link, intra-domain, and inter-domain, and may be defined on a link or service basis. The maintenance entities may be used to monitor performance within a network or across networks, and may be used to monitor various performance parameters, such as frame loss, frame delay, frame delay variation, availability, errored frame seconds, service status, frame throughput, the number of frames transmitted, received or dropped, the status of a loopback interface, the amount of time a service has been unavailable, and many other parameters. Several management mechanisms may be used, and the measurements may be collected using a solicited collection method, in which a response is required and collected, or an unsolicited collection method in which a response is not required. | 03-27-2014 |
20140341012 | RESILIENT DUAL-HOMED DATA NETWORK HAND-OFF - Systems and methods for L2 Ethernet resilient hand-off include an access network configured between a first end point and a second end point, a first communication path and a second communication path for data flow between the first end point and the second end point, wherein the first communication path is active and the second communication path is inactive, and if a fault is detected in the first communication path, logic configured to activate the second communication path and perform a resilient hand-off of the data flow from the first communication path to the second communication path. | 11-20-2014 |
20150019920 | CONNECTIVITY FAULT NOTIFICATION - Connectivity fault notification is provided by generating an alarm indication signal at a device that is logically adjacent to the fault, and forwarding the alarm indication signal upward through various levels to at least one client level entity. The alarm indication signal may be suppressed at any level for a service instance if service is restored at that level, or if a protection path prevents disruption of the service instance at that level, or auto-suppressed at an originating node based on number of times transmitted or elapsed time. The alarm indication signal may include a point of failure indicator such as the MAC address of the device that generates the alarm indication signal, or a failed resource identity such as an IEEE 802.1AB LLDP MAC Service Access Point (“MSAP”). Further, the alarm indication signal may be employed to trigger use of the protection path. | 01-15-2015 |
20150063097 | IN-BAND SIGNALING FOR POINT-MULTIPOINT PACKET PROTECTION SWITCHING - A method and system provide in-band protection switch signaling in a communication system arranged as a point-to-multipoint tree. The point-to-multipoint tree includes a root node communicatively coupled to a plurality of leaf nodes through both a working link and a protection link. Data is transferred through a current link of the point-to-multipoint tree. The current link is either the working link or the protection link. A fault is detected in the current link in the point-to-multipoint tree. Each leaf node in the point-to-multipoint tree is notified of the fault using the current link. Upon receiving the notification, the root node and each leaf node switch to the other link of the working link and the protection link. | 03-05-2015 |