Differentiated quality of service context assignment and propagation

• US 8,782,254 B2
• Filed: 06/28/2001
• Issued: 07/15/2014
• Est. Priority Date: 06/28/2001
• Status: Active Grant

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Duvvuru, Sreeram
• Primary Examiner(s): Winder, Patrice
• Assistant Examiner(s): WIDHALM, ANGELA M
• Application Number:
  US09/896,244
• Publication Number:
  US 20030018766A1
• Time in Patent Office: 4,765 Days
• Field of Search: 709/238, 709/230, 709/228, 709/229, 709217-219, 709223-226, 709232-235, 709/244
• US Class Current: 709/228
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/2425 for supporting services specification, e.g. SLA
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/808 User-type aware
• CPC Class Codes: H04L 47/826 Involving periods of time
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method, system and article of manufacture for providing differentiated quality of service in an application server may include receiving a request and accessing pre-determined policy data in a server system. The pre-determined policy data may depend upon the particular client sending the request. A request may include identity, role, requested service, and/or time constraint information. Based upon the request and policy data, a quality of service context may be established, possibly including service class, priority, and/or deadline attributes. The quality of service context may be propagated in the server system with the request.

Claims

1. A computer-implemented method for providing differentiated quality of service in an application server space, comprising:

a server system receiving a request for service from a client, wherein said request for service includes an encoding specifying a user identity, an encoding specifying a current user role under which the request was submitted, and an encoding specifying a requested service; and

in response to receiving the request for service;

accessing pre-determined policy data;

establishing a quality of service context for said request for service in the application server space, wherein said establishing comprises determining one or more attributes of said quality of service context based on both the specified user identity and the specified current user role included in said request for service, and based on said policy data; and

propagating said quality of service context with said request for service to a plurality of locations in the server system, wherein said propagating comprises;

sending data indicating the quality of service context to an application server in the server system along with the request for service; and

sending, by the application server, data indicating the quality of service context along with the request for service to an application component in the server system, such that the quality of service context is made available to both the application server and the application component.

2. The method of claim 1, wherein said request for service further includes information indicating a time constraint.

3. The method of claim 1 wherein said quality of service context includes information indicating service class and a deadline.

4. The method of claim 1 wherein said establishing a quality of service context is completed at an ingress point.

5. The method of claim 4 wherein said ingress point is at least one of a web server or a protocol manager service within said server system.

6. The method of claim 1 further comprising, propagating the same quality of service context with a subsequent sub-request of said request for service.

7. The method of claim 1 wherein said propagating includes inserting said quality of service context into data sent with the request for service adjacent to at least one of a security context and a transaction context.

8. The method of claim 1, wherein said propagating comprises a load balancing service dispatching said request for service, including said quality of service context, to an application server in a plurality of application servers in the server system, based on said quality of service context.

9. The method of claim 1, wherein said propagating comprises a request manager service dispatching said request for service, including said quality of service context, to a software component in a plurality of software components in the server system, based on said quality of service context.

10. A non-transitory computer-readable storage medium, comprising program instructions executable to implement:

a server system, configured to;

receive a request for service from a client, wherein said request for service includes an encoding specifying a user identity, an encoding specifying a current user role under which the request was submitted, and an encoding specifying a requested service; and

in response to receiving the request for service;

access pre-determined policy data;

establish a quality of service context for said request for service in an application server space, wherein establishing said quality of service context comprises determining one or more attributes of said quality of service context based on both the specified user identity and the specified current user role included in said request for service, and based on said policy data;

propagate said quality of service context with said request for service to a plurality of locations in the server system, wherein said propagating comprises;

sending data indicating said quality of service context to an application server in the server system along with said request for service; and

sending, by the application server, data indicating said quality of service context to an application component in the server system, such that the quality of service context is made available to both the application server and the application component.

11. The non-transitory computer-readable storage medium of claim 10, wherein said request for service further includes information indicating a time constraint.

12. The non-transitory computer-readable storage medium of claim 10, wherein said quality of service context includes information indicating service class and a deadline.

13. The non-transitory computer-readable storage medium of claim 10, wherein said establishing a quality of service context is completed at an ingress point.

14. The non-transitory computer-readable storage medium of claim 13, wherein said ingress point is at least one of a web server or a protocol manager service within said server system.

15. The non-transitory computer-readable storage medium of claim 10, further comprising program instructions executable to:

propagate the same quality of service context with a subsequent sub-request of said request for service.

16. The non-transitory computer-readable storage medium of claim 10, wherein said propagating includes inserting said quality of service context into data sent with the request for service adjacent to at least one of a security context and a transaction context.

17. The non-transitory computer-readable storage medium of claim 10, wherein said propagating comprises a load balancing service dispatching said request for service, including said quality of service context, to an application server in a plurality of application servers in the server system, based on said quality of service context.

18. The non-transitory computer-readable storage medium of claim 10, wherein said propagating comprises a request manager service dispatching said request for service, including said quality of service context, to a software component in a plurality of software components in the server system, based on said quality of service context.

19. A first computer system, comprising:

a processor;

a memory storing program instructions;

wherein the processor is operable to execute the program instructions to implement a server system configured to;

receive a request for service from a client, wherein said request for service includes an encoding specifying a user identity, an encoding specifying a current user role under which the request was submitted, and an encoding specifying a requested service; and

in response to receiving the request for service, the server system is further configured to;

access pre-determined policy data;

establish a quality of service context for said request for service in an application server space, wherein establishing said quality of service context comprises determining one or more attributes of said quality of service context based on both the specified user identity and the specified current user role included in said request for service, and based on said policy data;

propagate said quality of service context with said request for service to a plurality of locations in the server system, wherein said propagating comprises;

sending data indicating said quality of service context to an application server in the server system along with said request for service; and

sending, by the application server, data indicating said quality of service context to an application component in the server system, such that the quality of service context is made available to both the application server and the application component.

20. The system of claim 19, wherein said request for service further includes information indicating a time constraint.

21. The system of claim 19, wherein said quality of service context includes information indicating service class and a deadline.

22. The system of claim 19, wherein said establishing a quality of service context is completed at an ingress point.

23. The system of claim 22, wherein said ingress point is at least one of a web server or a protocol manager service within said server system.

24. The system of claim 19, further comprising program instructions to:

propagate the same quality of service context with a subsequent sub-request of said request for service.

25. The system of claim 19, wherein said propagating includes inserting said quality of service context into data sent with the request for service adjacent to at least one of a security context and a transaction context.

26. The system of claim 19, wherein said propagating comprises a load balancing service dispatching said request for service including, said quality of service context, to an application server in a plurality of application servers in the server system, based on said quality of service context.

27. The system of claim 19, wherein said propagating comprises a request manager service dispatching said request for service, including said quality of service context, to a software component in a plurality of software components in the server system, based on said quality of service context.