IP Library Granted Patent US 8,862,943
Granted Patent B2
US 8,862,943 · App. 11/137,015 · Granted Oct 14, 2014

Connectivity fault notification

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,862,943
App. No.
11/137,015
Granted
Oct 14, 2014
Kind
B2
Abstract

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.

Claims (42)

1. A method for providing connectivity fault notification, comprising:

detecting a fault in a first network at a node logically adjacent to the fault;

generating an alarm indication signal in response to detecting the fault; and

forwarding the alarm indication signal to only client level entities associated with a particular virtual local area network (VLAN) affected by the fault.

2. The method of claim 1 further including forwarding the alarm indication signal to only the associated client level entities via a higher maintenance entity (ME) level.

3. The method of claim 1 , further including suppressing the transmission of alarm indication signal for a service instance at a level if the service instance is not disrupted at that Level.

4. The method of claim 1 , further including suppressing the transmission of alarm indication signal for a service instance if the fault is repaired.

5. The method of claim 1 , further including suppressing the transmission of alarm indication signal for a service instance in response to administrative input.

6. The method of claim 1 , further including suppressing the transmission alarm indication signal for a service instance after a predetermined period of time.

7. The method of claim 1 , further including suppressing the transmission of alarm indication signal for a service instance after periodically transmitting a predetermined number of the alarm indication signal.

8. The method of claim 1 , further including forwarding the alarm indication signal via each port of the node associated with a service instance affected by the fault.

9. The method of claim 1 , further including forwarding the alarm indication signal via each port of the node.

10. The method of claim 1 , further including inserting a point of failure indicator in the alarm indication signal.

11. The method of claim 10 , wherein the point of failure indicator includes a media access control (MAC) address.

12. The method of claim 10 , wherein the point of failure indicator includes a failed resource identity.

13. The method of claim 1 , further including suppressing the transmission of alarm indication signal for a service instance, where the service instance is a Virtual Local Area Network (“VLAN”).

14. The method of claim 13 , wherein a different multicast alarm indication signal is generated for each VLAN.

15. The method of claim 13 , wherein a different unicast alarm indication signal is generated for each VLAN.

16. The method of claim 1 , further including inserting a cause of failure indicator in the alarm indication signal.

17. The method of claim 1 , further including triggering use of a protection path in response to receipt of the alarm indication signal.

18. The method of claim 1 , wherein, if the client level entities have insufficient information in the received Alarm Indication Signal (AIS) upon which to selectively suppress the alarms, then all of the alarms are suppressed.

19. The method of claim 1 , wherein if an identification of a client level entity isolated on the other side of the fault to which the node is logically adjacent is available in the received Alarm Indication Signal (AIS) then the alarms for which identification is known are selectively suppressed.

20. A network device operable to provide connectivity fault notification, comprising:

circuitry configured to detect a fault in a first network logically adjacent to the device;

logic configured to generate an alarm indication signal in response to detection of the fault; and

at least one port configured to forward the alarm indication signal to only client level entities associated with a particular virtual local area network (VLAN) affected by the fault.

21. The device of claim 20 , further including logic configured to suppress the alarm indication signal for a service instance at a level if a service instance is not disrupted at that level.

22. The device of claim 20 , further including logic configured to suppress the alarm indication signal for a service instance if the fault is repaired.

23. The device of claim 20 , further including logic configured to suppress the alarm indication signal for a service instance in response to administrative input.

24. The device of claim 20 , further including logic configured to suppress the alarm indication signal for a service instance after a predetermined period of time.

25. The device of claim 20 , further including logic configured to suppress the alarm indication signal for a service instance after transmitting a predetermined number of copies of the alarm indication signal.

26. The device of claim 20 , further including logic configured to forward the alarm indication signal via each port of the node associated with a service instance affected by the fault.

27. The device of claim 20 , further including logic configured to forward the alarm indication signal via each port of the device.

28. The device of claim 20 , further including logic configured to insert a point of failure indicator in the alarm indication signal.

29. The device of claim 28 , wherein the point of failure indicator includes a media access control (MAC′) address.

30. The device of claim 28 , wherein the point of failure indicator includes a failed resource identity.

31. The device of claim 20 , further including logic configured to insert a cause of failure indicator in the alarm indication signal.

32. The device of claim 20 , further including logic configured to trigger use of a protection path in response to receipt of the alarm indication signal.

33. The device of claim 20 , wherein a different multicast alarm indication signal is generated for each affected VLAN.

34. The device of claim 20 , wherein a different unicast alarm indication signal is generated for each affected VLAN.

35. The device of claim 20 , wherein, if the client level entities have insufficient information in the received Alarm Indication Signal (AIS) upon which to selectively suppress the alarms, then all of the alarms are suppressed.

36. The device of claim 20 , wherein if an identification of a client level entity isolated on the other side of the fault to which the node is logically adjacent is available in the received Alarm Indication Signal (AIS) then the alarms for which identification is known are selectively suppressed.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2014
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 032425/0867 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →