IP Library Granted Patent US 7,386,628
Granted Patent B1
US 7,386,628 · App. 10/142,218 · Granted Jun 10, 2008

Methods and systems for processing network data packets

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 7,386,628
App. No.
10/142,218
Granted
Jun 10, 2008
Kind
B1
Abstract

Methods and systems for identifying a local domain for a data packet received at an interface through a network are described herein. In one aspect of the invention, an exemplary method includes extracting the network protocol information from the data packet, determining a local domain ID based on multiple layers of network protocol information simultaneously, and assigning the local domain ID to the data packet. Other methods and systems are also described.

Claims (71)

1. A method for processing a data packet received at an interface of a network equipment over a network, the method comprising:

extracting network protocol information associated with multiple different network protocol layers from the data packet;

determining a local domain ID based on the extracted network protocol information associated with the multiple different network protocol layers, the local domain ID being uniquely assigned to a customer;

assigning the local domain ID to the data packet and to a flow of data packets arriving at the interface to which the data packet belongs; and

internally routing the data packet and each subsequently received data packet belonging to the flow from a first module of the network equipment to a second module of the network equipment based on the local domain ID assigned to the flow.

2. The method of claim 1 , wherein the network protocol information associated with multiple different network protocol layers comprises:

port information;

a virtual local area network (VLAN) ID;

a destination internet protocol (IP) address;

a source IP address; and

a media access control (MAC) address.

3. The method of claim 1 , further comprising:

determining whether the interface is shared by multiple local domains for external routing; and

determining the local domain ID based on the interface, VLAN ID, MAC address, and destination IP address extracted from a header of the data packet, if the interface is shared by multiple local domains for external routing.

4. The method of claim 1 , further comprising:

determining whether the interface is shared by multiple local domains for internal routing; and

determining the local domain ID based on the interface, VLAN ID, MAC address, and destination IP address extracted from a header of the data packet, if the interface is shared by multiple local domains for external routing.

5. A method for processing a data packet received at an interface of a network equipment through a network, the data packet having network protocol information, the method comprising:

determining a flow type of the data packet;

determining a local domain ID for the data packet using network protocol information associated with multiple different network protocol layers, the local domain ID being uniquely assigned to a customer;

selecting a service processing element (SPE) from among a plurality of SPEs within the network equipment to process the data packet, the selecting of the SPE being based on the flow type and the local domain ID of the data packet; and

transmitting the data packet, internally within the network equipment, from the interface to the selected SPE.

6. The method of claim 5 , wherein the network protocol information associated with multiple different network protocol layers comprises:

port information;

a virtual local area network (VLAN) ID;

a destination internet protocol (IP) address;

a source IP address; and

a media access control (MAC) address.

7. The method of claim 5 , further comprising:

determining whether the interface is shared by multiple local domains for external routing; and

determining the local domain ID based on the interface, VLAN ID, MAC address, and destination IP address extracted from a header of the data packet, if the interface is shared by multiple local domains for external routing.

8. The method of claim 5 , further comprising:

determining whether the interface is shared by multiple local domains for internal routing; and

determining the local domain ID based on the interface, VLAN ID, MAC address, and destination IP address extracted from a header of the data packet, if the interface is shared by multiple local domains for internal routing.

9. The method of claim 5 , wherein the selecting of the SPE comprises:

performing a hash operation based on the network protocol information and the flow type of the data packet; and

selecting the SPE based on a result of the hash operation.

10. The method of claim 5 , further comprising:

searching a flow table to identify a flow in which the data packet belongs;

retrieving the local domain ID from the flow table if the flow is identified.

11. The method of claim 10 , further comprising:

building a tuple based on the network protocol information extracted from the data packet; and

searching the flow table based on the tuple.

12. The method of claim 10 , further comprising:

building a message header based on the information retrieved from the flow table or based on the SPE selection;

appending the message header to the data packet; and

transmitting the data packet based on the message header.

13. A machine-readable storage medium having stored thereon executable code to cause a machine to perform a method for processing a data packet received at an interface of a network equipment over a network, the method comprising:

extracting network protocol information associated with multiple different network protocol layers from the data packet;

determining a local domain ID based on the extracted network protocol information associated with the multiple different network protocol layers, the local domain ID being uniquely assigned to a customer;

assigning the local domain ID to the data packet and to a flow of data packets arriving at the interface to which the data packet belongs, the local domain ID assigned to the flow being used to internally route the data packet and each subsequently received data packet belonging to the flow from a first module of the network equipment to a second module of the network equipment.

14. The machine-readable storage medium of claim 13 , wherein the network protocol information associated with multiple different network protocol layers comprises:

port information;

a virtual local area network (VLAN) ID;

a destination internet protocol (IP) address;

a source IP address; and

a media access control (MAC) address.

15. The machine-readable storage medium of claim 13 , wherein the method further comprises:

determining whether the interface is shared by multiple local domains for external routing; and

determining the local domain ID based on the interface, VLAN ID, MAC address, and destination IP address extracted from a header of the data packet, if the interface is shared by multiple local domains for external routing.

16. The machine-readable storage medium of claim 13 , wherein the method further comprises:

determining whether the interface is shared by multiple local domains for internal routing; and

determining the local domain ID based on the interface, VLAN ID, MAC address, and destination IP address extracted from a header of the data packet, if the interface is shared by multiple local domains for internal routing.

17. A machine-readable storage medium having stored thereon executable code to cause a machine to perform a method for processing a data packet received at an interface of a network equipment through a network, the data packet having network protocol information, the method comprising:

determining a flow type of the data packet;

determining a local domain ID for the data packet using network protocol information associated with multiple different network protocol layers, the local domain ID being uniquely assigned to a customer;

selecting a service processing element (SPE) from among a plurality of SPEs within the network equipment to process the data packet, the selecting of the SPE being based on the flow type and the local domain ID of the data packet; and

transmitting the data packet, internally within the network equipment, from the interface to the selected SPE.

18. The machine-readable storage medium of claim 17 wherein the method further comprises:

performing a hash operation based on the network protocol information and the flow type of the data packet; and

selecting the SPE based on a result of the hash operation.

Assignments (16)
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 48612/0598) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063691/0294 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 48612/FRAME 0582 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.
Reel/Frame 063456/0428 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 57700/FRAME 0935 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.
Reel/Frame 063458/0303 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Oct 4, 2021
From: AVAYA MANAGEMENT LP
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 057700/0935 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Mar 15, 2019
From: AVAYA MANAGEMENT L.P.
To: CITIBANK, N.A.
Reel/Frame 048612/0582 →
SECURITY INTEREST Recorded Mar 15, 2019
From: AVAYA MANAGEMENT L.P.
To: GOLDMAN SACHS BANK USA
Reel/Frame 048612/0598 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 12, 2019
From: AVAYA HOLDINGS LIMITED
To: AVAYA MANAGEMENT L.P.
Reel/Frame 048577/0492 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2010
From: NORTEL NETWORKS LIMITED
To: AVAYA HOLDINGS LIMITED
Reel/Frame 023998/0799 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 4, 2005
From: INKRA NETWORKS, INC.
To: NORTEL NETWORKS LIMITED
Reel/Frame 017185/0325 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 8, 2002
From: HANSELL, JEFFREY STUART; ROBERTS, DAVID GARY; KUMAR, MAHESH; SHEKOKAR, PRAVEEN GHANASHYAM; WONG, KALAINE
To: INKRA NETWORKS, INC.
Reel/Frame 013165/0702 →