IP Library Granted Patent US 8,626,883
Granted Patent B2
US 8,626,883 · App. 12/800,101 · Granted Jan 7, 2014

Injecting addresses to enable OAM functions

Inventors: Vach Kompella (Cupertino, CA); Joe Regan (Pleasanton, CA); Wenao Hu (San Jose, CA)
Assignee: Alcatel Lucent
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,626,883
App. No.
12/800,101
Granted
Jan 7, 2014
Kind
B2
Abstract

Inserting an address used for performing such OAM functions in an efficient way that is transparent to a customer or service using the network path is disclosed. An indication is received that a source address reserved for OAM use should be inserted into a forwarding database associated with a provider network node, such as a provider edge device, that receives the indication. The address is inserted into a forwarding database as an address that is owned by the provider network node and reserved for OAM use. One or more other nodes associated with a service with which the OAM address is associated may be notified that the OAM address is associated with the provider network node that owns the OAM address.

Claims (54)

1. A method for inserting into a forwarding database associated with a network service of a network an address reserved for testing use comprising:

receiving a packet forming a part of a testing message, the packet comprising the address reserved for testing use and an indication that the address is to be inserted into the forwarding database associated with the network service, wherein the packet is received at a first node and the address reserved for testing use was not used as an address to route the packet to the first node;

adding the address reserved for testing use to the forwarding database associated with the network service; and

using a communication interface to notify a second node associated with the network service that the address is associated with the first node, wherein the first node notifies the second node and the second node stores in a second node forwarding table an association between the address reserved for testing use and a path to the first node.

2. The method as recited in claim 1 further comprising marking the address as reserved for testing use.

3. The method as recited in claim 1 , wherein the packet is received at the first node, the method further comprising receiving an indication that the address is to be associated with the first node.

4. The method as recited in claim 1 , wherein the packet is received at the first node, the method further comprising receiving an indication at the first node that one or more other nodes associated with the network service should be sent information concerning the address.

5. The method as recited in claim 1 , wherein the packet is received at the first node, the method further comprising notifying one or more other nodes associated with the network service that the address is associated with the first node.

6. The method as recited in claim 1 , wherein the packet is received at the first node, the method, further comprising notifying one or more other nodes associated with the network service that the address is associated with a forwarding path associated with the first node.

7. The method as recited in claim 1 further comprising receiving an indication that the address should be purged from the forwarding database.

8. The method as recited in claim 1 further comprising receiving an indication that the address may only be purged by a sender of the packet.

9. The method as recited in claim 1 , wherein the packet is received according to a protocol and the method further comprising receiving an indication that a customer packet that uses the address should be processed normally according to the protocol.

10. The method as recited in claim 1 further comprising receiving an indication that the address should be added to the forwarding database as an address reserved for testing use even if the address was previously added to the forwarding database as an address available for customer use.

11. The method as recited in claim 1 , wherein the packet is received according to a protocol and the method further comprising receiving according to the protocol a second packet addressed to the address reserved for testing purpose.

12. The method as recited in claim 11 further comprising associating the second packet with the address.

13. The method as recited in claim 11 further comprising providing an indication regarding a processing of the second packet.

14. The method as recited in claim 11 further comprising providing an indication of an external interface with which the second packet is associated based on the address reserved for testing use.

15. The method as recited in claim 11 further comprising sending the second packet to an interface for processing.

16. The method as recited in claim 11 further comprising determining the second packet is configured to diagnose an aspect of the network by reading a flag in the second packet.

17. The method as recited in claim 16 , wherein the second packet is received according to a protocol and the flag is interpreted using the protocol.

18. The method as recited in claim 11 further comprising monitoring the second packet while a customer network and a provider network are active.

19. The method as recited in claim 11 wherein the second packet is received pursuant to a test of the continuity of at least a portion of the network service.

20. The method as recited in claim 11 wherein the second packet is received pursuant to a test of the connectivity of at least a portion of the network service.

21. The method as recited in claim 1 , wherein the packet is received according to a protocol and the packet mimics a normal packet.

22. The method as recited in claim 1 wherein the packet includes a flag indicating removal of an address.

23. The method as recited in claim 1 wherein the packet includes a flag indicating adding an address.

24. The method as recited in claim 1 further comprising receiving a query regarding the address reserved for testing use.

25. The method as recited in claim 24 further comprising providing in response to the query information associated with the address reserved for testing use.

26. The method as recited in claim 24 further comprising providing in response to the query an indication of a network node with which the address is associated.

27. The method as recited in claim 24 further comprising providing in response to the query an indication of a network path with which the address is associated.

28. The method as recited in claim 1 wherein the address reserved for testing use is a physical address.

29. The method as recited in claim 1 wherein the address reserved for testing use is a MAC address.

30. The method as recited in claim 1 , wherein the packet is received according to a protocol and wherein the indication that the address is to be inserted into the forwarding database for testing use comprises data included in a field added to the packet according to the protocol.

31. The method as recited in claim 1 , wherein the packet is received according to a protocol and wherein the indication that the address is to be inserted into the forwarding database for testing use comprises data included in a field of the packet that has been modified according to the protocol.

32. The method as recited in claim 1 , wherein the packet is received according to a protocol and wherein the indication that the address is to be inserted into the forwarding database for testing use comprises determining that a data field normally included in a packet sent according to the protocol has been removed.

33. A system inserting into a forwarding database associated with a network service an address reserved for testing use comprising:

a processor configured to:

receive a packet forming a part of a testing message, the packet comprising the address reserved for testing use and an indication that the address is to be inserted into the forwarding database associated with the network service, wherein the packet is received at a first node and the address reserved for testing use was not used as an address to route the packet to the first node;

add the address reserved for testing use to the forwarding database associated with the network service; and

notify a second node associated with the network service that the address is associated with the first node, wherein the first node notifies the second node and the second node stores in a second node forwarding table an association between the address reserved for testing use and a path to the first node.

34. The system as recited in claim 33 , wherein the packet is received at the first node, and an indication is received at the first node that one or more other nodes associated with the network service should be sent information concerning the address.

35. The system as recited in claim 33 , wherein the packet is received at the first node, and the processor is further configured to notify one or more other nodes associated with the network service that the address is associated with the first node.

36. The system as recited in claim 33 , wherein the processor is further configured to receive an indication that the address should be purged from the forwarding database.

37. The system as recited in claim 33 , wherein the packet is received according to a protocol and the processor is further configured to receive an indication that a customer packet that uses the address should be processed normally according to the protocol.

38. The system as recited in claim 33 , wherein the packet is received according to a protocol and the processor is further configured to receive according to the protocol a second packet addressed to the address reserved for testing purpose.

39. The system as recited in claim 33 , wherein the processor is further configured to receive a query regarding the address reserved for testing use.

40. The system as recited in claim 33 , wherein the address reserved for testing use is a MAC address.

41. A computer program product for inserting into a forwarding database associated with a network service an address reserved for testing use, the computer program product comprising a non-transitory computer readable storage medium on which are encoded computer instructions which when executed by a computer cause the computer to perform a method comprising:

receiving a packet forming a part of a testing message, the packet comprising the address reserved for testing use and an indication that the address is to be inserted into the forwarding database associated with the network service, wherein the packet is received at a first node and the address reserved for testing use was not used as an address to route the packet to the first node;

adding the address reserved for testing use to the forwarding database associated with the network service; and

notifying a second node associated with the network service that the address is associated with the first node, wherein the first node notifies the second node and the second node stores in a second node forwarding table an association between the address reserved for testing use and a path to the first node.

42. The computer program product as recited in claim 41 , wherein the packet is received according to a protocol and the method further comprising receiving according to the protocol a second packet addressed to the address reserved for testing purpose.

43. The computer program product as recited in claim 41 , further comprising receiving a query regarding the address reserved for testing use.

44. The computer program product as recited in claim 41 , wherein the address reserved for testing use is a MAC address.

Assignments (17)
PATENT SECURITY AGREEMENT Recorded Aug 6, 2024
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 068328/0674 →
RELEASE OF LIEN ON PATENTS Recorded Aug 5, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 068328/0278 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 7, 2017
From: KOMPELLA, VACH; REGAN, JOE; HU, OLIVER
To: ALCATEL IP NETWORKS, INC.
Reel/Frame 043219/0548 →
CHANGE OF NAME Recorded Aug 7, 2017
From: ALCATEL USA SOURCING, L.P.
To: ALCATEL USA SOURCING, INC.
Reel/Frame 043478/0812 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 7, 2017
From: ALCATEL USA MARKETING, INC.
To: ALCATEL USA SOURCING, L.P.
Reel/Frame 043219/0663 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 7, 2017
From: ALCATEL IP NETWORKS
To: ALCATEL USA MARKETING, INC.
Reel/Frame 043219/0621 →
MERGER Recorded Aug 7, 2017
From: ALCATEL USA SOURCING, INC.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 043219/0781 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033949/0016 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
Continuity (3)
Continuation 10742239 · Dec 18, 2003
Provisional Application 60466322 · Apr 28, 2003
Related Publication 20100228842A1 · Sep 9, 2010