IP Library Granted Patent US 8,416,691
Granted Patent B1
US 8,416,691 · App. 11/414,725 · Granted Apr 9, 2013

Associating hosts with subscriber and service based requirements

Inventors: Ron E. Haberman (San Jose, CA); Miroslav Vrana (Zumikon, CH); Joseph M. Regan (Pleasanton, CA); Wim Henderickx (Westerlo, BE); Pierre Alfons Leonard Verhelst (Wilrijk, BE)
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,416,691
App. No.
11/414,725
Granted
Apr 9, 2013
Kind
B1
Abstract

Associating hosts with subscriber and service based requirements is disclosed. An identifier is extracted from a DHCP or other network address lease communication associated with a subscriber host. The identifier is used to associate the subscriber host with a requirement that is subscriber based, service based, or both subscriber and service based. The subscriber host is included in a set of one or more subscriber hosts associated with the subscriber, the service, or both, as applicable to the requirement, and the requirement is required to be enforced collectively to the one or more subscriber hosts comprising the set.

Claims (44)

1. A method of associating a host with a requirement, comprising:

extracting using a processor a first identifier from a first dynamic host configuration protocol (DHCP) or other network address lease communication associated with a first subscriber host for a first service;

determining using a processor that first requirement will be applied to the first subscriber host for the first service based on the first identifier;

extracting using a processor a second identifier from a second dynamic host configuration protocol (DHCP) or other network address lease communication associated with the first subscriber host for a second service;

determining using a processor that a second requirement will be applied to the subscriber host for the second service;

extracting using a processor a third identifier from a third dynamic host configuration protocol (DHCP) or other network address lease communication associated with a second subscriber host for the first service; and

determining using a processor that the first requirement will be applied to the second subscriber host for the first service;

wherein the first identifier comprises a digital subscriber line access multiplexer (DSLAM) physical port identifier and wherein determining that the first requirement will be applied to the first subscriber host includes performing a lookup to map the DSLAM physical port identifier to a corresponding subscriber identifier and using the corresponding subscriber identifier to determine that the first requirement is to be applied to the first subscriber host for the first service.

2. A method as recited in claim 1 , wherein extracting the first identifier includes parsing the DHCP or other network address lease communication.

3. A method as recited in claim 2 , wherein extracting the first identifier includes parsing DHCP option 82 information.

4. A method as recited in claim 1 , further comprising retrieving the subscriber profile from a profile database.

5. A method as recited in claim 1 , further comprising using the identifier to retrieve from a database a template configured to enforce the requirement.

6. A method as recited in claim 1 , further comprising enforcing the requirement at least in part by associating with a policy instance configured to enforce the requirement a network address associated with the subscriber host in the DHCP or other network address lease communication.

7. A method as recited in claim 1 , further comprising enforcing the requirement at least in part by adding to a filter, access control list (ACL), or other list associated with the requirement a network address associated with the subscriber host in the DHCP or other network address lease communication.

8. A method as recited in claim 1 , wherein the requirement comprises an aggregate quality of service commitment applicable collectively to the set of one or more subscriber hosts and the method further comprises enforcing the requirement at least in part by configuring a queue to receive network traffic associated with set of one or more subscriber hosts and associating with the queue a scheduler policy instance configured to enforce the requirement.

9. A method as recited in claim 1 , further comprising associating network traffic associated with the set of one or more subscriber hosts with a policy instance configured to enforce the requirement.

10. A method as recited in claim 1 , further comprising configuring a Python or other script engine to extract the identifier.

11. A system configured to associate a host with a requirement, comprising:

a communication interface configured to receive a DHCP or other network address lease communication; and

a processor coupled to the communication interface and configured to:

extract a first identifier from a first DHCP or other network address lease communication associated with a first subscriber host for a first service; and

use the first identifier to determine a first requirement that will be applied to the first subscriber host for the first service;

extract using a processor a second identifier from a second dynamic host configuration protocol (DHCP) or other network address lease communication associated with the first subscriber host for a second service;

determine using a processor that a second requirement will be applied to the subscriber host for the second service;

extract using a processor a third identifier from a third dynamic host configuration protocol (DHCP) or other network address lease communication associated with a second subscriber host for the first service; and

determine using a processor that the first requirement will be applied to the second subscriber host for the first service;

wherein the first identifier comprises a DSLAM physical port identifier and wherein the processor is configured to determine that the first requirement will be applied to the first subscriber host at least in part by performing a lookup to map the DSLAM physical port identifier to a corresponding subscriber identifier and using the corresponding subscriber identifier to determine that the first requirement is to be applied to the first subscriber host for the first service.

12. A system as recited in claim 11 , wherein the system comprises a router.

13. A system as recited in claim 11 , wherein the system comprises a multi-service edge router.

14. A system as recited in claim 11 , further comprising a storage device configured to store data associated with the requirement.

15. A system as recited in claim 14 , wherein the data associated with the requirement comprises a subscriber profile.

16. A method as recited in claim 14 , wherein the data associated with the requirement comprises a template configured to enforce the requirement.

17. The system as recited in claim 11 , wherein extracting the first identifier includes parsing the DHCP or other network address lease communication.

18. The system of as recited in claim 11 , wherein extracting the first identifier includes parsing DHCP option 82 information.

19. A computer program product for associating a host with a requirement, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

extracting first identifier from a DHCP or other network address lease communication associated with a first subscriber host for a first service; and

using the first identifier to determine a first requirement that will be applied to the first subscriber host for the first service;

extracting using a processor a second identifier from a second dynamic host configuration protocol (DHCP) or other network address lease communication associated with the first subscriber host for a second service;

determining using a processor to determine that a second requirement will be applied to the subscriber host for the second service;

extracting using a processor a third identifier from a third dynamic host configuration protocol (DHCP) or other network address lease communication associated with a second subscriber host for the first service; and

determining using a processor that the first requirement will be applied to the second subscriber host for the first service;

wherein the first identifier comprises a DSLAM physical port identifier and wherein determining that the first requirement will be applied to the first subscriber host includes performing a lookup to map the DSLAM physical port identifier to a corresponding subscriber identifier and using the corresponding subscriber identifier to determine that the first requirement is to be applied to the first subscriber host for the first service.

20. The computer program product as recited in claim 19 , wherein extracting the first identifier includes parsing the DHCP or other network address lease communication.

21. The method of claim 19 , wherein extracting the first identifier includes parsing DHCP option 82 information.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Jun 3, 2021
From: TERRIER SSC, LLC
To: WSOU INVESTMENTS, LLC
Reel/Frame 056526/0093 →
SECURITY INTEREST Recorded Jun 1, 2021
From: WSOU INVESTMENTS, LLC
To: OT WSOU TERRIER HOLDINGS, LLC
Reel/Frame 056990/0081 →
RELEASE OF SECURITY INTEREST Recorded May 21, 2019
From: OCO OPPORTUNITIES MASTER FUND, L.P. (F/K/A OMEGA CREDIT OPPORTUNITIES MASTER FUND LP
To: WSOU INVESTMENTS, LLC
Reel/Frame 049246/0405 →
SECURITY INTEREST Recorded May 20, 2019
From: WSOU INVESTMENTS, LLC
To: BP FUNDING TRUST, SERIES SPL-VI
Reel/Frame 049235/0068 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2017
From: ALCATEL LUCENT
To: WSOU INVESTMENTS, LLC
Reel/Frame 044000/0053 →
SECURITY INTEREST Recorded Sep 21, 2017
From: WSOU INVESTMENTS, LLC
To: OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP
Reel/Frame 043966/0574 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0555 →
CHANGE OF NAME Recorded Feb 19, 2013
From: ALCATEL
To: ALCATEL LUCENT
Reel/Frame 029835/0588 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2006
From: HABERMAN, RON E.; VRANA, MIROSLAV; REGAN, JOSEPH M.; HENDERICKX, WIM; VERHELST, PIERRE ALFONS LEONARD
To: ALCATEL
Reel/Frame 017956/0614 →