Network resource management system

• US 20040003084A1
• Filed: 08/01/2002
• Published: 01/01/2004
• Est. Priority Date: 05/21/2002
• Status: Abandoned Application

• Current Assignee: Atlassian US, Inc. (Atlassian Corporation)
• Original Assignee: Atlassian US, Inc. (Atlassian Corporation)
• Inventors: Malik, Dale W., Friedman, Lee G.
• Application Number:
  US10/211,053
• Publication Number:
  US 20040003084A1
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

Network resource management systems are provided. A representative network resource management system includes a server operable to provide a remote terminal coupled to the network with a class of service marker specific to a user of the remote terminal, and a roster list comprising a plurality of resources present on the network. The server is also operable to receive a routing request from the remote terminal, the routing request comprising a request for at least one resource from the roster list and the class of service marker. The server being operable to check the class of service marker of the remote terminal before permitting access to the resource by the user. Methods and other systems for network resource management are also provided.

Claims

1. A network resource management system, comprising:

a server on a network operable to provide a remote terminal coupled to the network with a class of service marker specific to a user of the remote terminal, and a roster list comprising a plurality of resources present on the network;

the server being further operable to receive a routing request from the remote terminal, the routing request comprising a request for at least one resource from said roster list and the class of service marker; and

the server being further operable to check the class of service marker of the remote terminal to verify authorization before permitting access to said resource by said user.

2. The system of claim 1, wherein the resource is operable to check the server for the class of service marker corresponding to the user.

3. The system of claim 2, wherein routing to the resource is denied if the policy does not permit access to the resource by the class of service marker received from the remote terminal.

4. The system of claim 3, wherein routing to the resource is denied if the permanent database includes a different class of service marker than has been provided by the user.

5. The system of claim 3, wherein routing to the resource is denied if said at least one resource is not included within the roster list of the user.

6. The system of claim 1, wherein the resource is a software application residing on an application server.

7. The system of claim 1, wherein the resource is another user, and requesting the resource allows the user to attempt to chat with the other user.

8. The system of claim 1, wherein the network comprises a plurality of network connection sockets, the plurality of network connection sockets having at least two subgroups having different data rate connections, and the requested resource is a network connection socket in a particular subgroup.

9. The system of claim 1, wherein the server comprises:

a class of service database coupled to an authentication database, the server being operable to provide a class of service marker to a remote terminal associated with a particular user after authenticating the particular user with the authentication database.

10. The system of claim 9, wherein the server further comprises:

a service manager operable to send a resource list comprising a plurality of resources to the remote terminal.

11. The system of claim 10, wherein the service manager is further operable to send the resource list to the remote terminal and indicate a presence status of each of the plurality of resources with respect to the user, and the presence status of the resource indicates whether a resource is on-line or off-line.

12. The system of claim 11, wherein the service manager is further operable to indicate an availability status of each of the plurality of resources with respect to the user, and the availability status is determined based upon a class of service permission to use a resource.

13. The system of claim 10, wherein the service manager is further operable to send the resource list to the remote terminal and indicate an availability status for each of the plurality of resources on the resource list, and the availability status is determined based upon a class of service permission to use a resource.

14. The system of claim 10, further comprising:

a service router operable to receive the routing request for a resource, check the class of service marker associated with the routing request against the policy, and route the resource if the policy allows the resource to be routed to the user.

15. The system of claim 14, wherein the service router comprises a JabberD service router, and the service manager comprises a Jabber Service Manager.

16. The system of claim 1, wherein a class of service marker corresponding to the user can be adjusted by a database administrator to provide a different level of access to the plurality of resources.

17. The system of claim 16, wherein the database administrator can set the class of service marker to allow access to the plurality of resources based upon at least one circumstance.

18. The system of claim 17, wherein said at least one circumstance comprises a time period during which access is allowed.

19. The system of claim 18, wherein said at least one circumstance comprises allowing access only during business hours.

20. The system of claim 17, wherein said at least one circumstance comprises allowing access only from a particular network address associated with the user on the network.

21. The system of claim 1, wherein the class of service marker comprises an encoded security string, and the system is operable to decode and check the security string upon receiving the routing request.

22. The system of claim 1, wherein a network administrator can invoke a change of presence with respect to at least one class of service level.

23. A class of service system, comprising:

a remote terminal associated with a user, the remote terminal being operable to register with a server and receive a class of service marker and to request and receive a roster list, the roster list comprising a plurality of resources that are present on the network;

the remote terminal being further operable to send a routing request to a service router, the routing request including the class of service marker and a request for routing to a resource; and

the remote terminal being further operable to receive the resource if the class of service marker allows routing of the resource.

24. The system of claim 23, wherein the roster list further comprises a plurality of resources that are present and available on the network.

25. The system of claim 24, wherein the roster list delineates between which of the plurality of resources on the roster list are merely present, and which resources on the roster list are available.

26. The system of claim 24, wherein the roster list includes the plurality of resources which are both residing on a server that is present and available on the network, and to which the service router allows routing, according to the class of service marker corresponding to the user.

27. The system of claim 23, wherein the remote terminal is operable to use a modified Jabber client to communicate with the server.

28. The system of claim 23, wherein the remote terminal is operable to use a modified Jabber client to request the class of service marker from the server, to request the roster list, and to send the routing request.

29. The system of claim 28, wherein the modified Jabber client comprises an operating system for the remote terminal, operable to generate a display comprising a plurality of resources for display to the user.

30. The system of claim 23, wherein at least one of the plurality of resources is a person, and choosing that resource causes a chat invitation to be sent to the person.

31. The system of claim 23, wherein the resource is an application residing on an application server coupled to the network.

32. The system of claim 23, wherein the resource is a network connection socket among a plurality of network connection sockets, the plurality of network connection sockets having at least two connection datarates.

33. The system of claim 23, wherein registration comprises providing a user authentication and an internet protocol address.

34. A method for managing access to network resources, comprising:

receiving a registration request over a network from a user of a remote terminal;

searching a database to find a class of service marker associated with the user;

sending the class of service marker to the remote terminal; and

sending a roster list comprising a plurality of resources which are present.

35. The method of claim 34, further comprising:

sending the roster list to the user via the network, the roster list comprising a plurality of off-line resources which are marked as not-present because a server providing the resource is not coupled to the network.

36. The method of claim 35, further comprising:

sending a roster list to the user via the network, the roster list comprising a plurality of resources marked as not-present because the class of service marker corresponding to the user does not permit routing of the plurality of resources marked as not-present.

37. The method of claim 35, further comprising:

sending the roster list to the user via the network, the roster list comprising a plurality of unavailable resources, unavailable because the user does not have a class of service permission to use the plurality of unavailable resources.

38. The method of claim 34, further comprising:

receiving a resource request from the remote terminal, which includes the class of service marker, to deliver a requested resource to the remote terminal.

39. The method of claim 38, further comprising:

checking a security layer to assure that the requested resource is present and available to the class of service marker received from the remote terminal.

40. The method of claim 39, wherein checking a security layer comprises:

checking the class of service marker received from the user against a class of service marker stored in the database.

41. The method of claim 39, wherein checking a security layer comprises:

checking a security string associated with the class of service marker to authenticate the class of service marker received.

42. The method of claim 39, further comprising:

routing the requested resource to the remote terminal when the requested resource is present and available to the class of service marker received from the remote terminal.

43. The method of claim 42, further comprising:

checking the class of service marker received from the remote terminal against the class of service marker associated with the user by the database to ensure that the user has not altered the class of service marker.

44. The method of claim 34, further comprising:

receiving a request from the remote terminal, which includes the class of service marker, to deliver a requested resource to the remote terminal;

checking a security layer to assure that the requested resource is present and available to the class of service marker received from the remote terminal;

routing the requested resource to the remote terminal the requested resource is present and available to the class of service marker received from the remote terminal; and

checking the class of service marker received from the remote terminal against the class of service marker associated with the user by the database to ensure that the user has not altered the class of service marker.

45. The method of claim 44, further comprising:

providing a connection to a resource that corresponds to chatting with another user when the class of service marker indicates that the connection is permitted.

46. The method of claim 44, further comprising:

providing a connection to a resource that corresponds to a software application when the class of service marker indicates that the connection is permitted.

47. The method of claim 44, further comprising:

providing a connection to a resource that corresponds to a network connection socket of a particular bandwidth when the class of service marker indicates that the connection is permitted.

48. The method of claim 34, further comprising:

using a Jabber Service Manager check the class of service marker and to provide the roster list to the remote terminal.

49. The method of claim 34, further comprising:

using a Jabber D service router to check the class of service marker and route the resource to the remote terminal.

50. The method of claim 34, further comprising:

receiving a resource request, including the class of service marker; and

checking a security layer definition against the class of service marker for authorization to access the requested resource.

51. The method of claim 50, further comprising;

refusing access when the user is requesting a resource outside of a time window included in the security layer definition allowing access to the class of service marker.

52. The method of claim 50, further comprising;

refusing access when the user is requesting a resource from a terminal not included in the security layer definition allowing access to the class of service marker.

53. A method for requesting use of a resource, the method comprising:

registering with a server residing on a network;

receiving a class of service marker and a roster list corresponding to a plurality of resources which are present on the network;

requesting a resource from the roster list; and

including the class of service marker with the resource request.

54. The method of claim 53, further comprising:

receiving the resource if the class of service marker allows routing of the resource.

55. The method of claim 53, further comprising:

receiving a roster list comprising a plurality of resources which are present and available on the network.

56. The method of claim 55, further comprising:

receiving a roster list which details which of the plurality of resources on the roster list are merely present, and which of the plurality of resources are available.

57. The method of claim 55, further comprising:

receiving a roster list detailing which of the plurality of resources are both residing on a server that is present and available on the network, and to which a service router allows routing, according to the class of service marker corresponding to the user.

58. The method of claim 53, further comprising:

using a modified Jabber client to communicate with the server.

59. The method of claim 53, further comprising:

using a modified Jabber client to register with the server, to receive the class of service marker from the server with the roster list, and to send the resource request to the server.

60. The method of claim 59, further comprising:

using the modified Jabber client as an operating system for the remote terminal and to generate a display comprising the roster list;

61. The method of claim 53, further comprising:

requesting a resource that corresponds to a person with whom the user would like to chat.

62. The method of claim 53, further comprising:

requesting a resource that corresponds to an application residing on an application server coupled to the network.

63. The method of claim 53, further comprising:

requesting a resource that corresponds to a particular network connection socket among a plurality of network connection sockets having at least two connection datarates.

64. The method of claim 53, further comprising:

providing authentication of the user prior to receiving a class of service marker from the server.