Dynamic application port service provisioning for packet switch
Abstract
A packet switching node has first and second forwarding engines interconnected over a first path dependent on an inspection engine and a second path independent of the inspection engine. The first forwarding engine identifies a first session in which an application port number is to be dynamically negotiated for a second session and directs the first session to the first path. The inspection engine monitors a dynamic application port number negotiation for the first session, determines a dynamic application port number for the second session, configures a service level for the second session on the forwarding engines and directs the second session to the second path. The first forwarding engine also identifies a third session in which an application port number is statically assigned and directs the third session to the second path.
Claims
exact text as granted — not AI-modifiedWe claim:
1 . A packet switching node for receiving and transmitting packets for one or more sessions, the packet switching node comprising:
an inspection engine for determining an application port by monitoring a first session in which the application port is negotiated; and first and second forwarding engines interconnected on a first path dependent on the inspection engine and a second path independent of the inspection engine, wherein the first forwarding engine identifies the first session, and directs the first session to the first path.
2 . The packet switching node according to claim 1 , wherein the application port is dynamically negotiated between a server node and a host node.
3 . The packet switching node according to claim 1 , wherein the first forwarding engine forwards a second session, for which the application port has been negotiated, over the second path.
4 . The packet switching node according to claim 1 , wherein the first forwarding engine identifies a third session with a statically assigned application port, and wherein the first forwarding engine forwards the third session over the second path.
5 . The packet switching node according to claim 1 , wherein the packets are forwarded via the inspection engine and at least one of the forwarding engines on the first path, and the packets are forwarded via at least one of the forwarding engines but not via the inspection engine on the second path.
6 . The packet switching node according to claim 3 , wherein the inspection engine configures a service level for the second session on the first forwarding engine.
7 . The packet switching node according to claim 6 , wherein the inspection engine configures the service level for the first session on the second forwarding engine.
8 . The packet switching node according to claim 7 , wherein the configuration of the service level includes association of the application port with a quality of service (QoS) on at least one of the forwarding engines.
9 . The packet switching node according to claim 7 , wherein the configuration of the service level includes association of the application port with a customer on at least one of the forwarding engines.
10 . The packet switching node according to claim 7 , wherein the configuration of the service level includes association of the application port with a statistics group on at least one of the forwarding engines.
11 . The packet switching node according to claim 10 , wherein the statistics group comprises amount of traffic, size of file transfer, time of day, customer identification or number of bytes.
12 . The packet switching node according to claim 10 , wherein the statistics group is used to perform billing, auditing, network management or traffic profiling.
13 . A method of assigning an application port to one or more sessions, the method comprising the steps of:
receiving a plurality of packets for the sessions on a first forwarding engine; identifying a first session in which the application port is to be negotiated; directing the first session to an inspection engine; and determining the application port for a second session by monitoring the application port negotiation using the inspection engine.
14 . The method of assigning an application port according to claim 13 , the method further comprising the step of:
forwarding the second session to a second forwarding engine without going through the inspection engine.
15 . The method of assigning an application port according to claim 13 , the method further comprising the steps of:
identifying a third session in which the application port is statically assigned; and forwarding the third session to a second forwarding engine without going through the inspection engine.
16 . The method of assigning an application port according to claim 13 , the method further comprising the step of:
configuring a service level for the second session on the first forwarding engine.
17 . The method of assigning an application port according to claim 16 , the method further comprising the step of:
configuring the service level for the second session on a second forwarding engine.
18 . The method of assigning an application port according to claim 17 , wherein the steps of configuring a service level comprise the step of associating the application port with quality of service (QoS).
19 . The method of assigning an application port according to claim 17 , wherein the steps of configuring a service level comprise the step of associating the application port with a customer.
20 . The method of assigning an application port according to claim 17 , wherein the steps of configuring a service level comprises the step of associating the application port with a statistics group.
21 . The packet switching node according to claim 20 , wherein the statistics group comprises amount of traffic, size of file transfer, time of day, customer identification or number of bytes.
22 . The packet switching node according to claim 20 , wherein the statistics group is used to perform billing, auditing, network management or traffic profiling.
23 . A packet switching node for receiving and transmitting packets for one or more sessions, the packet switching node comprising:
inspection means for determining an application port by monitoring a first session in which the application port is negotiated; and first and second forwarding means interconnected on a first path dependent on the inspection means and a second path independent of the inspection means, wherein the first forwarding means identifies the first session, and directs the first session to the first path.
24 . The packet switching node according to claim 23 , wherein the application port is dynamically negotiated between a server node and a host node.
25 . The packet switching node according to claim 23 , wherein the first forwarding means forwards a second session, for which the application port has been negotiated, over the second path.
26 . The packet switching node according to claim 23 , wherein the first forwarding means identifies a third session with a statically assigned application port, and wherein the first forwarding means forwards the third session over the second path.
27 . The packet switching node according to claim 23 , wherein the packets are forwarded via the inspection means and at least one of the forwarding means on the first path, and the packets are forwarded via at least one of the forwarding means but not via the inspection means on the second path.
28 . The packet switching node according to claim 25 , wherein the inspection means configures a service level for the second session on the first forwarding means.
29 . The packet switching node according to claim 28 , wherein the inspection means configures the service level for the first session on the second forwarding means.
30 . The packet switching node according to claim 28 , wherein the configuration of the service level includes association of the application port with a quality of service (QoS) on at least one of the forwarding means.
31 . The packet switching node according to claim 28 , wherein the configuration of the service level includes association of the application port with a customer on at least one of the forwarding means.
32 . The packet switching node according to claim 28 , wherein the configuration of the service level includes association of the application port with a statistics group on at least one of the forwarding means.
33 . The packet switching node according to claim 32 , wherein the statistics group comprises amount of traffic, size of file transfer, time of day, customer identification or number of bytes.
34 . The packet switching node according to claim 32 , wherein the statistics group is used to perform billing, auditing, network management or traffic profiling.Join the waitlist — get patent alerts
Track US2002016856A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.