IP Library Granted Patent US 7,167,473
Granted Patent B1
US 7,167,473 · App. 10/112,347 · Granted Jan 23, 2007

Method for device addressing using SNMP community string-based routing

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,167,473
App. No.
10/112,347
Granted
Jan 23, 2007
Kind
B1
Abstract

A method of addressing a data packet includes receiving the data packet and creating a packet header for the data packet. The method also includes providing routing information in a community string format in the packet header and communicating the packet header and data packet to a gateway, wherein the gateway is operable to forward the data packet to a destination uniquely defined by the routing information.

Claims (49)

1. A method of addressing a data packet, comprising:

receiving the data packet;

creating a packet header for the data packet;

providing routing information in an encoded format in the packet header, wherein the routing information uniquely identifies a destination device; and

communicating the packet header and data packet to a gateway device;

wherein the data packet is formatted in the Simple Network Management Protocol format.

2. The method of claim 1 , wherein the gateway device is operable to communicate the data packet to the destination device identified by the routing information.

3. A method of addressing a data packet, comprising:

receiving the data packet;

creating a packet header for the data packet;

providing routing information in an encoded format in the packet header, wherein the routing information uniquely identifies a destination device; and

communicating the packet header and data packet to a gateway device;

wherein the data packet includes a request packet to be communicated to a destination device.

4. The method of claim 3 , further comprising:

storing an address of an originating device of the request packet;

receiving a response packet from the destination device; and

communicating the response packet to the originating device.

5. The method of claim 4 , further comprising:

waiting to receive a first response packet from the destination device in response to a first request packet communicated to the destination device before communicating a second request packet to the destination device.

6. A method of addressing a data packet, comprising:

receiving the data packet;

creating a packet header for the data packet;

providing routing information in an encoded format in the packet header, wherein the routing information uniquely identifies a destination device; and

communicating the packet header and data packet to a gateway device;

wherein the gateway device is operable to communicate the data packet to the destination device identified by the routing information;

wherein the data packet is communicated to the destination device on an inband management channel.

7. The method of claim 6 , wherein the inband management channel is an LES-EOC management channel.

8. A method of addressing a data packet, comprising:

receiving the data packet;

creating a packet header for the data packet;

providing routing information in an encoded format in the packet header, wherein the routing information uniquely identifies a destination device; and

communicating the packet header and data packet to a gateway device;

wherein the routing information is of the form ProtocolType@<gatewayid>.<slot#>.<port#>.<virtual path identifier>.<virtual circuit identifier>.

9. The method of claim 8 , wherein the <gatewayid> component of the routing information includes an identification of the gateway device along a communication path to the destination device.

10. The method of claim 9 , wherein the <slot#>.<port#> component of the routing information includes an identification of a physical slot and a physical port of the gateway device along a communication path to the destination device.

11. The method of claim 10 , wherein the <virtual path identifier>.<virtual circuit identifier> component of the routing information includes an identification of a specific device as the destination device of the data packet.

12. A method of storing a data packet in a data packet host, comprising:

receiving the data packet;

identifying an originating device of the data packet;

providing location information for the originating device in a community string format in a packet header;

assigning an internet protocol address to the data packet that is the same as an internet protocol address for a routing device; and

routing the packet header and data packet to a storage device.

13. The method of claim 12 , wherein the data packet is formatted in Simple Network Management format.

14. The method of claim 12 , wherein the location information is communicated on an inband management channel.

15. The method of claim 14 , wherein the inband management channel is an LES-EOC management channel.

16. The method of claim 12 , wherein the routing information is of the form ProtocolType@<gatewayid>.<slot#>.<port#>.<virtual path identifier>.<virtual circuit identifier>.

17. The method of claim 16 , wherein the <gatewayid> component of the routing information includes an identification of a gateway device along a communication path from the originating device.

18. The method of claim 16 , wherein the <slot#>.<port#> component of the routing information includes an identification of a physical slot and a physical port of the gateway device along a communication path from the originating device.

19. The method of claim 16 , wherein the <virtual path identifier>.<virtual circuit identifier> component of the routing information includes an identification of a specific device as the originating device of the data packet.

Assignments (10)
SHORT-FORM PATENTS SECURITY AGREEMENT Recorded Sep 5, 2024
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 068857/0290 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT AT R/F 044978/0801 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058949/0497 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT Recorded Dec 29, 2017
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: GENBAND US LLC
Reel/Frame 044986/0303 →
CORRECTIVE ASSIGNMENT TO CORRECT PATENT NO. 6381239 PREVIOUSLY RECORDED AT REEL: 039269 FRAME: 0234. ASSIGNOR(S) HEREBY CONFIRMS THE PATENT SECURITY AGREEMENT. Recorded Jan 3, 2017
From: GENBAND US LLC
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 041422/0080 →
RELEASE AND REASSIGNMENT OF PATENTS Recorded Jul 7, 2016
From: COMERICA BANK, AS AGENT
To: GENBAND US LLC
Reel/Frame 039280/0467 →
PATENT SECURITY AGREEMENT Recorded Jul 6, 2016
From: GENBAND US LLC
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 039269/0234 →
RELEASE OF SECURITY INTEREST Recorded Jan 10, 2014
From: ONE EQUITY PARTNERS III, L.P., AS COLLATERAL AGENT
To: GENBAND US LLC
Reel/Frame 031968/0955 →