Apparatus and method for supporting multiple traffic categories at a single networked device

• US 8,103,790 B2
• Filed: 12/20/2005
• Issued: 01/24/2012
• Est. Priority Date: 12/20/2005
• Status: Active Grant

• Current Assignee: BCE Incorporated
• Original Assignee: BCE Incorporated
• Inventors: Turk, Doughan A.
• Primary Examiner(s): Tran, Philip B
• Application Number:
  US11/568,919
• Publication Number:
  US 20090129369A1
• Time in Patent Office: 2,226 Days
• Field of Search: 709/238, 709/224, 709/245
• US Class Current: 709/238
• CPC Class Codes: H04L 45/304 Route determination for signalling traffic
• CPC Class Codes: H04L 45/3065 for real time traffic
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5061 Pools of addresses
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols

Abstract

An apparatus comprising a first and a second functional entity operable for supporting traffic in, respectively, first and second traffic categories across a communications network. The second traffic category is associated with specific routing requirements. A network interface releases a request for a first address and a request for a second address. The request for a second address comprises data that is instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address. The network is pre-configured to route traffic destined for a given address in the particular set of at least one address in accordance with the specific routing requirements. Receipt of the first address from the address-assigning entity enables the first functional entity to act as a receptor of traffic in the first traffic category, while receipt of the second address enables the second functional entity to act as a receptor of traffic in the second traffic category.

Claims

1. An apparatus, comprising:

a first functional entity operable for supporting traffic in a first traffic category across a communications network;

a second functional entity operable for supporting traffic in a second traffic category across the communications network, the second traffic category being associated with specific routing requirements through the communications network; and

a network interface operable for;

releasing a request for a first address which, when received from an address-assigning entity, enables the first functional entity to act as a receptor of traffic in the first traffic category that is destined for the apparatus;

releasing a request for a second address which, when received from the address-assigning entity, enables the second functional entity to act as a receptor of traffic in the second traffic category that is destined for the apparatus;

wherein said request for a second address comprises data instrumental in causing the second address to be assigned by the address-assigning entity from a particular set of at least one address;

wherein the communications network is pre-configured to route traffic destined for a given address in the particular set of at least one address in accordance with said specific routing requirements.

2. The apparatus defined in claim 1, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to be routed securely through the communications network.

3. The apparatus defined in claim 2, wherein the first and second functional entities implement a VoIP soft client.

4. The apparatus defined in claim 2, wherein the first and second functional entities implement a data handling application.

5. The apparatus defined in claim 1, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to reach a designated network element in the communications network.

6. The apparatus defined in claim 5, wherein the designated network element comprises a quarantine server.

7. The apparatus defined in claim 6, wherein the second functional entity implements an electronic mail application.

8. The apparatus defined in claim 5, wherein the designated network element comprises a real-time packet filter.

9. The apparatus defined in claim 8, wherein the second functional entity implements an Internet browser.

10. The apparatus defined in claim 1, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to follow an explicit route through the communications network.

11. The apparatus defined in claim 1, wherein the specific routing requirements comprise a priority level associated with traffic in the second traffic category.

12. The apparatus defined in claim 1, wherein the first functional entity and the second functional entity are different.

13. The apparatus defined in claim 12, wherein the second functional entity implements a VoIP soft client.

14. The apparatus defined in claim 13, wherein the first functional entity implements an Internet browser.

15. The apparatus defined in claim 12, wherein the second functional entity implements an Internet browser.

16. The apparatus defined in claim 12, wherein the second functional entity implements an electronic mail application.

17. The apparatus defined in claim 12, wherein the second functional entity implements an electronic gaming application.

18. The apparatus defined in claim 12, wherein the second functional entity implements a video application.

19. The apparatus defined in claim 1, the specific routing requirements through the communications network being second specific routing requirements, the particular set of at least one address being a second set of at least one address, wherein the first traffic category is associated with first specific routing requirements through the communications network, wherein said request for a first address comprises data instrumental in causing the first address to be assigned by the address-assigning entity from a first set of at least one address.

20. The apparatus defined in claim 19, wherein said first specific routing requirements comprise a requirement for traffic in the first traffic category to be routed through the communications network in accordance with a first security criterion, and wherein said second specific routing requirements comprise a requirement for traffic in the second traffic category to be routed through the communications network in accordance with a second security criterion different from the first security criterion.

21. The apparatus defined in claim 20, wherein the first functional entity and the second functional entity are the same.

22. The apparatus defined in claim 21, wherein the first and second functional entities implement a VoIP soft client.

23. The apparatus defined in claim 21, wherein the first and second functional entities implement a data handling application.

24. The apparatus defined in claim 20, wherein the first functional entity and the second functional entity are different.

25. The apparatus defined in claim 24, wherein the first functional entity implements a VoIP soft client and wherein the second functional entity implements a data handling application.

26. The apparatus defined in claim 25, wherein the second security criterion represents a higher level of security than the first security criterion.

27. The apparatus defined in claim 19, the apparatus further comprising:

a third functional entity operable for supporting traffic in a third traffic category across the communications network, the third traffic category being associated with third specific routing requirements through the communications network;

said network interface being operable for releasing a request for a third address which, when received from the address-assigning entity, enables the third functional entity to act as a receptor of traffic in the third traffic category that is destined for the apparatus;

wherein said request for a third address comprises data instrumental in causing the third address to be assigned by the address-assigning entity from a third set of at least one address;

wherein the communications network is pre-configured to route traffic destined for a given address in the third set of at least one address in accordance with said third specific routing requirements.

28. The apparatus defined in claim 27, wherein the first, second and third functional entities are selected from the group consisting of a VoIP soft client, an Internet browser, an electronic mail application, an electronic gaming application and a video application.

29. The apparatus defined in claim 1, wherein the first and second addresses are IP addresses.

30. The apparatus defined in claim 29, wherein the particular set of at least one address comprises a plurality of IP addresses.

31. The apparatus defined in claim 30, wherein the plurality of IP address are contiguous.

32. The apparatus defined in claim 1, wherein said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address comprises an indicator associated with the second traffic category.

33. The apparatus defined in claim 1, wherein said releasing a request for a second address comprises:

receiving an original address request from the second functional entity;

recognizing that the second functional entity supports the second traffic category;

appending to the original address request said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address, thereby to create said request for a second address.

34. The apparatus defined in claim 1, wherein said releasing a request for a second address comprises receiving the request for a second address from the second functional entity and forwarding the request for a second address to the address-assigning entity.

35. The apparatus defined in claim 1, further comprising an intermediate software component, the intermediate software component being operable to:

receive an original address request from the second functional entity;

recognize that the second functional entity supports the second traffic category;

append to the original address request said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address, thereby to create said request for a second address;

forward said request for a second address to the network interface.

36. The apparatus defined in claim 1, further comprising an intermediate software component, the intermediate software component being operable to:

receive an original address request from the second functional entity, the original address request containing a data element indicative of an address of the apparatus;

recognize that the second functional entity supports the second traffic category;

modify the data element to reflect said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address, thereby to create said request for a second address;

forward said request for a second address to the network interface.

37. The apparatus defined in claim 1, wherein the communications network is an Internet backbone network.

38. The apparatus defined in claim 1, further comprising an input/output interface for allowing a set of at least one external peripheral device to communicate traffic in the first traffic category and traffic in the second traffic category.

39. The apparatus defined in claim 1, wherein said network interface is implemented as a PC network interface card.

40. A network architecture, comprising:

a plurality of routers capable of routing traffic through a backbone network, the routers being configured to route traffic destined for a given address in a particular set of at least one address in accordance with specific routing requirements;

a computing apparatus, comprising;

a first functional entity operable for supporting traffic in a first traffic category across the backbone network;

a second functional entity operable for supporting traffic in a second traffic category across the backbone network, the second traffic category being associated with said specific routing requirements through the backbone network; and

a network interface operable for;

releasing a request for a first address which, when received from an address-assigning entity, enables the first functional entity to act as a receptor of traffic in the first traffic category that is destined for the computing apparatus;

releasing a request for a second address which, when received from the address-assigning entity, enables the second functional entity to act as a receptor of traffic in the second traffic category that is destined for the computing apparatus;

wherein said request for a second address comprises data instrumental in causing the second address to be assigned by the address-assigning entity from said particular set of at least one address.

41. The network architecture defined in claim 40, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to be routed securely through the backbone network.

42. The network architecture defined in claim 41, wherein the first and second functional entities implement a VoIP soft client.

43. The network architecture defined in claim 41, wherein the first and second functional entities implement a data handling application.

44. The network architecture defined in claim 40, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to reach a designated network element in the backbone network.

45. The network architecture defined in claim 44, wherein the designated network element comprises a quarantine server.

46. The network architecture defined in claim 45, wherein the second functional entity implements an electronic mail application.

47. The network architecture defined in claim 44, wherein the designated network element comprises a real-time packet filter.

48. The network architecture defined in claim 47, wherein the second functional entity implements an Internet browser.

49. The network architecture defined in claim 40, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to follow an explicit route through the backbone network.

50. The network architecture defined in claim 40, wherein the specific routing requirements comprise a priority level associated with traffic in the second traffic category.

51. The network architecture defined in claim 40, wherein the first functional entity and the second functional entity are different.

52. The network architecture defined in claim 51, wherein the second functional entity implements a VoIP soft client.

53. The network architecture defined in claim 52, wherein the first functional entity implements an Internet browser.

54. The network architecture defined in claim 51, wherein the second functional entity implements an Internet browser.

55. The network architecture defined in claim 51, wherein the second functional entity implements an electronic mail application.

56. The network architecture defined in claim 51, wherein the second functional entity implements an electronic gaming application.

57. The network architecture defined in claim 51, wherein the second functional entity implements a video application.

58. The network architecture defined in claim 40, the specific routing requirements through the backbone network being second specific routing requirements, the particular set of at least one address being a second set of at least one address, wherein the first traffic category is associated with first specific routing requirements through the backbone network, wherein said request for a first address comprises data instrumental in causing the first address to be assigned by the address-assigning entity from a first set of at least one address.

59. The network architecture defined in claim 58, wherein said first specific routing requirements comprise a requirement for traffic in the first traffic category to be routed through the backbone network in accordance with a first security criterion, and wherein said second specific routing requirements comprise a requirement for traffic in the second traffic category to be routed through the backbone network in accordance with a second security criterion different from the first security criterion.

60. The network architecture defined in claim 59, wherein the first functional entity and the second functional entity are the same.

61. The network architecture defined in claim 60, wherein the first and second functional entities implement a VoIP soft client.

62. The network architecture defined in claim 60, wherein the first and second functional entities implement a data handling application.

63. The network architecture defined in claim 59, wherein the first functional entity and the second functional entity are different.

64. The network architecture defined in claim 63, wherein the first functional entity implements a VoIP soft client and wherein the second functional entity implements a data handling application.

65. The network architecture defined in claim 64, wherein the second security criterion represents a higher level of security than the first security criterion.

66. The network architecture defined in claim 58, the computing apparatus further comprising:

a third functional entity operable for supporting traffic in a third traffic category across the backbone network, the third traffic category being associated with third specific routing requirements through the backbone network;

said network interface being operable for releasing a request for a third address which, when received from the address-assigning entity, enables the third functional entity to act as a receptor of traffic in the third traffic category that is destined for the computing apparatus;

wherein said request for a third address comprises data instrumental in causing the third address to be assigned by the address-assigning entity from a third set of at least one address;

wherein the routers are configured to route traffic destined for a given address in the third set of at least one address in accordance with said third specific routing requirements.

67. The network architecture defined in claim 66, wherein the first, second and third functional entities are selected from the group consisting of a VoIP soft client, an Internet browser, an electronic mail application, an electronic gaming application and an IPTV application.

68. The network architecture defined in claim 40, wherein the first and second addresses are IP addresses.

69. The network architecture defined in claim 68, wherein the particular set of at least one address comprises a plurality of IP addresses.

70. The network architecture defined in claim 69, wherein the particular set of at least one address comprises an IP address subnet.

71. The network architecture defined in claim 40, wherein said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address comprises an indicator associated with the second traffic category.

72. The network architecture defined in claim 40, wherein said releasing a request for a second address comprises:

receiving an original address request from the second functional entity;

recognizing that the second functional entity supports the second traffic category;

appending to the original address request said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address, thereby to create said request for a second address.

73. The network architecture defined in claim 40, wherein said releasing a request for a second address comprises receiving the request for a second address from the second functional entity and forwarding the request for a second address to the address-assigning entity.

74. The network architecture defined in claim 40, further comprising an intermediate software component, the intermediate software component being operable to:

receive an original address request from the second functional entity;

recognize that the second functional entity supports the second traffic category;

append to the original address request said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address, thereby to create said request for a second address;

forward said request for a second address to the network interface.

75. The network architecture defined in claim 40, further comprising an intermediate software component, the intermediate software component being operable to:

receive an original address request from the second functional entity, the original address request containing a data element indicative of an address of the computing apparatus;

recognize that the second functional entity supports the second traffic category;

modify the data element to reflect said data instrumental in causing the second address to be assigned by an address-assigning entity from a particular set of at least one address, thereby to create said request for a second address;

forward said request for a second address to the network interface.