CA2570711A1 - Apparatus and method for supporting multiple traffic categories at a single networked device - Google Patents

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

Info

Publication number
CA2570711A1
CA2570711A1 CA002570711A CA2570711A CA2570711A1 CA 2570711 A1 CA2570711 A1 CA 2570711A1 CA 002570711 A CA002570711 A CA 002570711A CA 2570711 A CA2570711 A CA 2570711A CA 2570711 A1 CA2570711 A1 CA 2570711A1
Authority
CA
Canada
Prior art keywords
address
traffic
request
functional entity
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CA002570711A
Other languages
French (fr)
Other versions
CA2570711C (en
Inventor
Doughan A. Turk
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BCE Inc
Original Assignee
BCE Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by BCE Inc filed Critical BCE Inc
Publication of CA2570711A1 publication Critical patent/CA2570711A1/en
Application granted granted Critical
Publication of CA2570711C publication Critical patent/CA2570711C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/304—Route determination for signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H04L45/3065—Route determination based on the nature of the carried application for real time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/105—Multiple levels of security

Abstract

An apparatus comprising a first and a second functional entity operable fo r 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 dat a 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 traff ic category.

Claims (89)

WHAT IS CLAIMED IS:
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 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 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.
4. 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.
The apparatus defined in claim 1, wherein the specific routing requirements comprise a priority level associated with traffic in the second traffic category.
6. The apparatus defined in claim 2, wherein the first and second functional entities implement a VoIP soft client.
7. The apparatus defined in claim 2, wherein the first and second functional entities implement a data handling application.
8. The apparatus defined in claim 3, wherein the designated network element comprises a quarantine server.
9. The apparatus defined in claim 8, wherein the second functional entity implements an electronic mail application.
10. The apparatus defined in claim 3, wherein the designated network element comprises a real-time packet filter.
11. The apparatus defined in claim 10, wherein the second functional entity implements an Internet browser.
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. T'he 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 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. T'he 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. An apparatus, comprising:

- means for supporting traffic in a first traffic category across a communications network;

- means 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;

- means 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;
and - means for 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 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.
41. A method for responding to an address request, comprising:

- determining a traffic category associated with the address request;

- consulting a database in an attempt to identify a set of at least one available address corresponding to the determined traffic category;

- responsive to identification of a set of at least one available address corresponding to the determined traffic category, selecting an available address in the set;

- releasing the selected address to an originator of the address request.
42. The method defined in claim 41, further comprising:

- designating the selected address as not available.
43. The method defined in claim 41, wherein determining a traffic category associated with the address request comprises extracting an indicator from the address request, the indicator being indicative of the determined traffic category.
44. The method defined in claim 41, wherein the determined traffic category belongs to a set of at least two traffic categories comprising a first traffic category and a second traffic category.
45. The method defined in claim 44, wherein at least one of the first and second traffic categories is associated with data traffic.
46. The method defined in claim 45, wherein the first traffic category is associated with secure data traffic and the second traffic category is associated with non-secure data traffic.
47. The method defined in claim 45, wherein the other of the first and second traffic categories is associated with VoIP traffic.
48. The method defined in claim 44, wherein at least one of the first and second traffic categories is associated with VoIP traffic.
49. The method defined in claim 45, wherein the first traffic category is associated with secure VoIP traffic and the second traffic category is associated with non-secure VoIP traffic.
50. The method defined in claim 44, wherein at least one of the first and the second traffic categories is associated with electronic gaming traffic.
51. The method defined in claim 44, wherein at least one of the first and the second traffic categories is associated with electronic mail traffic.
52. The method defined in claim 44, wherein at least one of the first and the second traffic categories is associated with video traffic.
53. A computer-readable medium comprising computer-readable program code which, when interpreted by a computing apparatus, causes the computing apparatus to execute a method of responding to an address request, the computer-readable program code comprising:

- first computer-readable program code for causing the computing apparatus to determine a traffic category associated with the address request;

- second computer-readable program code for causing the computing apparatus to consult a database in an attempt to identify a set of at least one available address corresponding to the determined traffic category;

- third computer-readable program code for causing the computing apparatus to select an available address in a set of at least one available address corresponding to the determined traffic category;

- fourth computer-readable program code for causing the computing apparatus to release the selected address to an originator of the address request.
54. 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.
55. The network architecture defined in claim 54, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to be routed securely through the backbone network.
56. The network architecture defined in claim 54, 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.
57. The network architecture defined in claim 54, wherein said specific routing requirements comprise a requirement for traffic in the second traffic category to follow an explicit route through the backbone network.
58. The network architecture defined in claim 54, wherein the specific routing requirements comprise a priority level associated with traffic in the second traffic category.
59. The network architecture defined in claim 55, wherein the first and second functional entities implement a VoIP soft client.
60. The network architecture defined in claim 55, wherein the first and second functional entities implement a data handling application.
61. The network architecture defined in claim 56, wherein the designated network element comprises a quarantine server.
62. The network architecture defined in claim 61, wherein the second functional entity implements an electronic mail application.
63. The network architecture defined in claim 56, wherein the designated network element comprises a real-time packet filter.
64. The network architecture defined in claim 63, wherein the second functional entity implements an Internet browser.
65. The network architecture defined in claim 54, wherein the first functional entity and the second functional entity are different.
66. The network architecture defined in claim 65, wherein the second functional entity implements a VoIP soft client.
67. The network architecture defined in claim 66, wherein the first functional entity implements an Internet browser.
68. The network architecture defined in claim 65, wherein the second functional entity implements an Internet browser.
69. The network architecture defined in claim 65, wherein the second functional entity implements an electronic mail application.
70. The network architecture defined in claim 65, wherein the second functional entity implements an electronic gaming application.
71. The network architecture defined in claim 65, wherein the second functional entity implements a video application.
72. The network architecture defined in claim 54, 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.
73. The network architecture defined in claim 72, 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.
74. The network architecture defined in claim 73, wherein the first functional entity and the second functional entity are the same.
75. The network architecture defined in claim 74, wherein the first and second functional entities implement a VoIP soft client.
76. The network architecture defined in claim 74, wherein the first and second functional entities implement a data handling application.
77. The network architecture defined in claim 73, wherein the first functional entity and the second functional entity are different.
78. The network architecture defined in claim 77, wherein the first functional entity implements a VoIP soft client and wherein the second functional entity implements a data handling application.
79. The network architecture defined in claim 78, wherein the second security criterion represents a higher level of security than the first security criterion.
80. The network architecture defined in claim 72, 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.
81. The network architecture defined in claim 80, 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.
82. The network architecture defined in claim 54, wherein the first and second addresses are IP addresses.
83. The network architecture defined in claim 82, wherein the particular set of at least one address comprises a plurality of IP addresses.
84. The network architecture defined in claim 83, wherein the particular set of at least one address comprises an IP address subnet.
85. The network architecture defined in claim 54, 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.
86. The network architecture defined in claim 54, 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.
87. The network architecture defined in claim 54, 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.
88. The network architecture defined in claim 54, 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.
89. The network architecture defined in claim 54, 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.
CA2570711A 2005-12-20 2005-12-20 Apparatus and method for supporting multiple traffic categories at a single networked device Active CA2570711C (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CA2005/001933 WO2007071004A1 (en) 2005-12-20 2005-12-20 Apparatus and method for supporting multiple traffic categories at a single networked device

Publications (2)

Publication Number Publication Date
CA2570711A1 true CA2570711A1 (en) 2007-06-20
CA2570711C CA2570711C (en) 2012-07-31

Family

ID=38175472

Family Applications (1)

Application Number Title Priority Date Filing Date
CA2570711A Active CA2570711C (en) 2005-12-20 2005-12-20 Apparatus and method for supporting multiple traffic categories at a single networked device

Country Status (3)

Country Link
US (1) US8103790B2 (en)
CA (1) CA2570711C (en)
WO (1) WO2007071004A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8416691B1 (en) * 2006-04-27 2013-04-09 Alcatel Lucent Associating hosts with subscriber and service based requirements
US8265793B2 (en) * 2007-03-20 2012-09-11 Irobot Corporation Mobile robot for telecommunication
US8583831B2 (en) * 2007-10-05 2013-11-12 Samsung Electronics Co., Ltd. Thin client discovery
US8788707B1 (en) * 2010-05-27 2014-07-22 Crimson Corporation Assigning a random static IP address in a quarantine network
US8972061B2 (en) 2012-11-02 2015-03-03 Irobot Corporation Autonomous coverage robot
US9577923B2 (en) * 2013-03-14 2017-02-21 Qualcomm Incorporated Advanced gateway for multiple broadband access
US9704043B2 (en) 2014-12-16 2017-07-11 Irobot Corporation Systems and methods for capturing images and annotating the captured images with information
US20190319881A1 (en) * 2018-04-13 2019-10-17 Microsoft Technology Licensing, Llc Traffic management based on past traffic arrival patterns

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6081524A (en) * 1997-07-03 2000-06-27 At&T Corp. Frame relay switched data service
US6556547B1 (en) 1998-12-15 2003-04-29 Nortel Networks Limited Method and apparatus providing for router redundancy of non internet protocols using the virtual router redundancy protocol
US6351464B1 (en) 1999-09-20 2002-02-26 Mci Worldcom, Inc. Virtual second line hybrid network communication system
US6816456B1 (en) * 2000-02-04 2004-11-09 At&T Corp. Methods and apparatus for network use optimization
DE60116877T2 (en) * 2000-08-11 2006-09-14 British Telecommunications P.L.C. SYSTEM AND METHOD FOR RECORDING EVENTS
US7633942B2 (en) * 2001-10-15 2009-12-15 Avaya Inc. Network traffic generation and monitoring systems and methods for their use in testing frameworks for determining suitability of a network for target applications
US6813264B2 (en) 2001-11-02 2004-11-02 Qualcomm, Incorporated System and method for routing voice over IP calls
US7617317B2 (en) * 2001-12-03 2009-11-10 Sprint Spectrum L.P. Method and system for allowing multiple service providers to serve users via a common access network
SE522998C2 (en) 2001-12-14 2004-03-23 Hotsip Ab Procedure, gateway and computer software product to send a instant message between two users
US7366894B1 (en) * 2002-06-25 2008-04-29 Cisco Technology, Inc. Method and apparatus for dynamically securing voice and other delay-sensitive network traffic
GB2391742B (en) * 2002-08-07 2004-07-07 Samsung Electronics Co Ltd Network adress translation router for voice over internet protocol system
JP2004100967A (en) * 2002-09-04 2004-04-02 Sumitomo Metal Ind Ltd Burner for combusting powder, method of combusting powder and incinerator
WO2005001933A2 (en) 2003-06-28 2005-01-06 Infineon Technologies Ag Multichip semi-conductor component and method for the production thereof
US7529200B2 (en) * 2003-07-24 2009-05-05 3E Technologies International, Inc. Method and system for fast setup of group voice over IP communications
US6956820B2 (en) * 2003-10-01 2005-10-18 Santera Systems, Inc. Methods, systems, and computer program products for voice over IP (VoIP) traffic engineering and path resilience using network-aware media gateway
JP4634456B2 (en) * 2004-09-09 2011-02-16 アバイア インコーポレーテッド Method and system for security of network traffic
US20060088034A1 (en) * 2004-10-26 2006-04-27 Nortel Networks Limited Network service classes
US20070002833A1 (en) * 2005-06-30 2007-01-04 Symbol Technologies, Inc. Method, system and apparatus for assigning and managing IP addresses for wireless clients in wireless local area networks (WLANs)
US8238352B2 (en) * 2005-09-02 2012-08-07 Cisco Technology, Inc. System and apparatus for rogue VoIP phone detection and managing VoIP phone mobility
US7698548B2 (en) * 2005-12-08 2010-04-13 Microsoft Corporation Communications traffic segregation for security purposes

Also Published As

Publication number Publication date
CA2570711C (en) 2012-07-31
WO2007071004A1 (en) 2007-06-28
US20090129369A1 (en) 2009-05-21
US8103790B2 (en) 2012-01-24

Similar Documents

Publication Publication Date Title
US8094660B2 (en) VLAN server
CA2570711A1 (en) Apparatus and method for supporting multiple traffic categories at a single networked device
US8621020B2 (en) Method and apparatus for selective E-mail processing
US8559429B2 (en) Sequential frame forwarding
US7742474B2 (en) Virtual network interface cards with VLAN functionality
CN106878483A (en) A kind of IP address distribution method and device
CN104780103B (en) Message forwarding method and device
WO2017133647A1 (en) Packet processing method, traffic classifier, and service function instance
RU2008124975A (en) SYSTEMS AND METHODS FOR PROVIDING A NETWORK BRIDGE FOR TRAFFIC OF MULTI-ADDRESS DIRECTIONS BY UDP PROTOCOL
CN107241270A (en) Message processing method and device
KR20040055635A (en) Facilitating dslam-hosted traffic management functionality
CN106464745A (en) Dns server, client and data synchronization method
TW201138377A (en) Link state identifier collision handling
CN108234422A (en) Resource regulating method and device
JP2845208B2 (en) Address resolution device
US20070104200A1 (en) Network device with routing function and policy route setting method thereof
CN101141396A (en) Packet processing method and network appliance
CN105959248B (en) The method and device of message access control
US20110225267A1 (en) Server system for viewing in-house information, and method of controlling same
CN106254252A (en) The delivery method of a kind of Flow spec route and device
JP3228249B2 (en) Router device
CN110166375A (en) A kind of message forwarding method and device
CN100589445C (en) Method and device for the multi-interface to realize the promised access speed
JP4080402B2 (en) Name resolution / authentication method and apparatus
JP2010183214A (en) Apparatus, method and program for analysis of packet

Legal Events

Date Code Title Description
EEER Examination request