Systems and methods for scheduling applications

• US 8,627,320 B2
• Filed: 04/30/2010
• Issued: 01/07/2014
• Est. Priority Date: 10/31/2001
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Beser, Nurettin Burcak
• Primary Examiner(s): Truong, Camquy
• Application Number:
  US12/771,931
• Publication Number:
  US 20100235512A1
• Time in Patent Office: 1,348 Days
• Field of Search: None
• US Class Current: 718/102
• CPC Class Codes: H04L 12/2801 Broadband local area networks

Abstract

A system allocates resources in a network. The system receives an allocation request for a first flow and a second flow from an application and identifies the application based on the allocation request. The system schedules resources for the first flow based on the identification of the application and the second flow.

Claims

1. A method comprising:

receiving, via a Cable Modem Termination System (CMTS), a first allocation request for a first flow from a first application and a second allocation request for a second flow from a second application,

the first allocation request including a resource reservation protocol message that includes a gate identifier;

identifying, via the CMTS, a type of the first application based on the gate identifier that is included in the resource reservation protocol message of the first allocation request; and

scheduling, via the CMTS, resources, for the first flow, based on the identified type of the first application and information associated with the second flow.

2. The method of claim 1, where scheduling the resources further comprises:

identifying a quality of service parameter set based on a service class name associated with the first allocation request, and

scheduling the resources for the first flow further based on the quality of service parameter set.

3. The method of claim 2, where the second allocation request includes one of a Registration message, a Dynamic Service Addition message, or a Dynamic Service Change message.

4. The method of claim 2, where identifying the type of the first application further includes:

comparing a service class name associated with the first allocation request to stored application identifiers, and

identifying the type of the first application further based on comparing the service class name to the stored application identifiers.

5. The method of claim 1, where scheduling the resources for the first flow includes:

predicting a size of a data packet that is to be generated by the first application based on the type of the first application, and

scheduling the resources based on the predicted size of the data packet and the information associated with the second allocation request.

6. The method of claim 1, where the gate identifier is associated with a gate of the CMTS.

7. The method of claim 1, further comprising:

including, via the CMTS, a service flow encoding that includes a service class name associated with the first allocation request and includes a Quality of Service (QoS) parameter set of a service class associated with the service class name.

8. The method of claim 1, where identifying the type of the first application includes:

identifying the type of the first application further based on a service class name included in the first allocation request.

9. The method of claim 1, where identifying the type of the first application includes:

determining an application name using the gate identifier,

comparing the application name to stored application identifiers, and

identifying the type of the first application further based on comparing the application name to the stored application identifiers.

10. The method of claim 1,

where the resource reservation protocol message further includes application identification information that identifies at least one of:

an application vendor,

an application identifier,

an application version number, or

a sub-application identifier, and

where identifying the type of the first application includes;

identifying the type of the first application further based on the at least one of the application vendor, the application identifier, the application version number, or the sub-application identifier.

11. The method of claim 10,

where the application identification information identifies the sub-application identifier, and

where identifying the type of the first application further includes:

identifying the type of the first application based on the sub-application identifier.

12. The method of claim 10, where identifying the type of the first application further includes:

comparing the application identification information to stored application identifiers.

13. The method of claim 10, where identifying the type of the first application further includes:

comparing the application identification information to information in a gate control protocol.

14. A system comprising:

a network device to;

receive a first request, for a first flow, from a first application and a second request from a second application,

the first request being received via a cable modem termination system over a cable network, and

the first request including a resource reservation protocol message that includes a gate identifier;

identify a type of the first application based on the gate identifier that is included in the resource reservation protocol message of the first request; and

schedule resources, for the first flow, based on the type of the first application and information associated with the second request.

15. The system of claim 14,

where the first request further includes a service class name, and

where, when identifying the type of the first application, the network device is further to:

compare the service class name to a group of stored application identifiers.

16. The system of claim 14, where, when identifying the type of the first application, the network device is further to:

determine an application name using the gate identifier, and

compare the application name to a group of stored application identifiers.

17. The system of claim 14,

where the resource reservation protocol message further includes application identification information, and

where, when identifying the type of the first application, the network device is further to:

compare the application identification information to a group of stored application identifiers.

18. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by at least one component of a network device, cause the at least one component to;

receive a first request for a first flow from an application via a cable modem network,

the first request including a resource reservation protocol message that includes a gate identifier;

receive a second request from a second application via the cable modem network;

identify a type of the first application based on the gate identifier that is included in the resource reservation protocol message of the first request; and

schedule an amount of resources, for the first flow, based on the type of the first application and information associated with the second request.

19. The non-transitory computer-readable medium of claim 18, where the one or more instructions to identify the type of the first application include:

one or more instructions that, when executed by the at least one component, cause the at least one component to;

identify the type of the first application as one of a higher priority application or a lower priority application.

20. The non-transitory computer-readable medium of claim 18,

where the second request includes a service class name, and

where the instructions further comprise:

one or more instructions that, when executed by the at least one component, cause the at least one component to;

compare the service class name to a group of stored application identifiers,

identify another type of the second application based on comparing the service class name, and

scheduling other resources for the second application based on the other type.

21. The non-transitory computer-readable medium of claim 18,

where the second request includes a service class name, and

where the instructions further comprise:

one or more instructions that, when executed by the at least one component, cause the at least one component to;

include, for the second request, a service flow encoding that includes the service class name and includes a Quality of Service (QoS) parameter set of a service class associated with the service class name.