Framework for flexible and scalable real-time traffic emulation for packet switched networks

• US 6,845,352 B1
• Filed: 03/22/2000
• Issued: 01/18/2005
• Est. Priority Date: 03/22/2000
• Status: Expired due to Term

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Wang, Jay
• Primary Examiner(s): THOMSON, WILLIAM D
• Application Number:
  US09/533,396
• Time in Patent Office: 1,763 Days
• Field of Search: 703/2, 703/13, 703/21, 703/22, 703/20, 703/23, 703/24, 703/25, 703/27, 703/17, 702/182, 702/186, 702/183, 702/185, 709/223, 709/224, 709/220, 709/221, 709/222, 704/4, 704/38, 704/32, 704/33, 704/37, 704/39, 704/47, 370/244, 370/245, 370/250, 370/396, 370/395, 370/395.3, 370/395.51, 370/395.52
• US Class Current: 703/24
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]

Abstract

An implementation framework, including methodologies and the architecture, for a real-time traffic emulation for packet switched networks. The framework uses extended finite state machines to model the traffic flows that are to be emulated. A simple yet flexible FMS-based scripting language is proposed to describe these flows. An event-driven approach to schedule CPU among flows is also adopted.

Claims

1. System for providing traffic emulation for packet-switched networks, said system comprising:

an endpoint; and

an emulator module associated with said endpoint;

said emulator module comprising at least one finite state machine for modeling a number of traffic flows to be emulated, said emulator module operable to maintain simultaneous emulation of the number of traffic flows using a constant number of processes, the number of traffic flows being larger than the constant number of processes, the number of processes being small relative to the number of traffic flows that can be emulated, the number of processes required for emulation being independent of the number of traffic flows to be emulated.

2. The system according to claim 1, wherein said emulator module comprises an emulation manager, said emulation manager comprising a finite state machine for maintaining the status of an emulation operation.

3. The system according to claim 2, wherein said finite state machine of said emulation manager comprises three stages, said three stages comprising an initialization stage, and emulation stage and a result reporting stage.

4. The system according to claim 1, wherein:

said endpoint further comprises a network interface module for facilitating the communication of flows to a network; and

said at least one finite state machine comprises a plurality of finite state machines, wherein each finite state machine corresponds to a different one of said flows.

5. The system according to claim 4, wherein said network interface module comprises:

at least one port for receiving data;

at least one port for receiving signals;

a first background process for managing the receipt of data at said at least one data port; and

a second background process for managing the receipt of signals at said at least one signal port.

6. The system according to claim 1, wherein said emulator module further comprises an event scheduler, said event scheduler comprising an event queue.

7. Method of providing traffic emulation for packet-switched networks, said method comprising:

providing an endpoint; and

providing an emulator module associated with said endpoint;

said step of providing an emulator module comprising providing at least one finite state machine for modeling a number of traffic flows to be emulated, said emulator module operable to maintain simultaneous emulation of the number of traffic flows using a constant number of processes, the number of traffic flows being larger than the constant number, of processes the number of processes being small relative to the number of traffic flows that can be emulated, the number of processes required for emulation being independent of the number of traffic flows to be emulated; and

modeling traffic flows with said at least one finite state machine.

8. The method according to claim 7, wherein:

said step of providing an emulator module comprises providing an emulation manager;

said step of providing an emulation manager comprises providing a finite state machine for maintaining the status of said emulation; and

said method further comprising maintaining the status of said emulation with said finite state machine of said emulation manager.

9. The method according to claim 8, wherein:

said step of providing a finite state machine for maintaining the status of said emulation comprises providing three stages, said three stages comprising an initialization stage, and emulation stage and a result reporting stage; and

said method further comprises;

performing each of said three stages in the following sequence;

initialization stage, emulation stage and result reporting stage; and

thereafter returning to said initialization stage.

10. The method according to claim 7, wherein:

said step or providing an endpoint comprises providing a network interface module for facilitating the communication of flows to a network; and

said step of providing at least one finite state machine comprises providing a plurality of finite state machines, wherein each said finite state machine corresponds to a different one of said flows.

11. The method according to claim 10, wherein said step of providing a network interface module comprises providing:

at least one port for receiving data;

at least one port for receiving signals;

a first background process for managing the receipt of data at said at least one data port; and

a second background process for managing the receipt of signals at said at least one signal port;

said method further comprising;

managing the receipt of data at said at least one data port with said first background process; and

managing the receipt of signals at said at least one signal port with said second background process.

12. The method according to claim 7, wherein said step of providing an emulator module comprises providing an event scheduler, said event scheduler comprising an event queue.