Timeline presentation and control of simulated load traffic

BACKGROUND OF THE INVENTION

The present invention relates to telecommunication system testing, and more particularly to a timeline presentation and control of simulated load traffic.

In telecommunication systems having nodes, such as central terminals or base stations, and a plurality of terminals or handsets, communication between users at the terminals or handsets is routed along different routes via the nodes. If a large number of users are making calls simultaneously, a particular node may be overwhelmed and some information content may get lost. To simulate such a system in order to provide a design that does not get overwhelmed by a large number of users requires the specification of test traffic flows for a huge number of active subscribers. Such specification is complex and unwieldy to generate, is laborious and time consuming.

What is desired is a technique for determining the telecommunication system behavior under various traffic loads corresponding to a huge number of active subscribers that is easy and intuitive to use.

BRIEF SUMMARY OF THE INVENTION

Accordingly the present invention provides a timeline presentation and control of simulated traffic by sub-dividing call traffic into sub-groups of call traffic that have a common characteristic. Such sub-groups may include rush hour callers, lunch time callers, teenagers, internet surfers, business customers and other background callers that do not fit into any one sub-group. Each sub-group is represented as a timeline on a display where the traffic for the sub-group is simulated with ramp up and decline rates corresponding to the rate at which calls are added to the system or disconnected from the system and with steady state volume between the ramp up and decline, all as a function of time-of-day. The timelines may be manipulated by graphically changing the rates, steady state volume and time-of-day for the events. In this manner realistic traffic loads on the system may be simulated to determine times and nodes when and where the system may be overwhelmed.

The objects, advantages and other novel features of the present invention are apparent from the following detailed description when read in conjunction with the appended claims and attached drawing.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

Fig. 1 is a graphic display view of a timeline presentation according to the present invention.

DETAILED DESCRIPTION OF THE INVENTION

In order to reduce the problem of specifying test traffic flows for a huge active number of subscribers, or users, on a mobile telecommunication system, the present invention provides a way to allow an operator of a traffic load simulator to manipulate smaller sub-sets of subscribers that have a common characteristic. One common way to think about mobile users is perhaps by time-of-day events that are common for many people - such as rush hours. The time-of-day events may be over a portion of a day or over many days, since some system operators run multi-day tests. Knowing system behavior under the transient harmonic-convergence of peaky traffic groups is the objective of testing. Therefore by splitting traffic into time-of-day events, a timeline may be built to simulate how real-world traffic comes and goes during the day on the system.

Major traffic groups of users may be segregated into small clusters that may be represented by a few traffic profiles that have something in common - short voice calls, "gold" service, SMS traffic, etc. For each traffic group ramp rates for how fast the traffic ramps up or declines as well as steady state traffic volume between ramp up and decline are high level adjustments. Adjusting a temporal relationship between traffic groups may be a convenient slide-along-the-timeline interface, as is well known in the art. The groupings may occur across many traffic nuances and/or Internet Service Operator (ISO) protocol layers. For example the operator may want to observe video traffic generally, or "Platinum-Level" video traffic for compliance with Service Level Agreements (SLAs).

Referring now to Fig. 1 a graphic display of system traffic load on a traffic load simulator device shows that the traffic load is split into several sub-groups, such as background traffic, rush hour traffic, lunch time traffic, teenager traffic, internet surfer traffic, "gold" level business traffic, etc. In other words for a test period of time an operator specifies that some background traffic persists throughout the test period; that a couple of time-of-day blocks are specified for both morning and evening rush hours - maybe lots of people making short calls or mobile calls requiring hand-offs between nodes that overload base stations; that another group makes calls during the lunch hour; that teenagers after-school make hour-long multi-party calls; and that late-night surfers and gold-level Service Level Agreement business customers who pay the bills form other separate groups.

Once modeled like this, it becomes a day in the life of the system element under test. Of course the operator may add impulse traffic events, such as a bad call that ends a Super Bowl game in controversy which may generate a lot of calls in a short period of time, Chinese New Years which may generate a lot of congratulatory calls in a short period of time, etc. These impulse events may be moved around the timeline to coincide or miss other events. The ability to easily go in and change something, like the level of business traffic, makes it easy for an operator to test the system. Also optional looping may be added so tests may simulate real days, or just so a test runs indefinitely.

The user may have separate timelines for each of the caller traffic sub-groups as shown, or may merge the separate timelines into a single master timeline so that the impact of variations introduced within the different sub-groups on the overall traffic load pattern may be observed. The operator, using typical computer graphical interface techniques, readily manipulates the different ramp and decline rates and the "steady-state" call volume for each sub-group on the timelines. Although shown as one-dimensional timelines with a constant amplitude for the respective steady-states volumes, the timelines may be represented graphically in two-dimensions as "amplitude" versus time, where "amplitude" represents the number of calls, for example. The ramp up and decline rates correspond to the rates at which calls are added to the overall volume, i.e., connected to the system, or subtracted from the overall volume, i.e., disconnected from the system. By knowing the capacity of the nodes in the system, the timelines may point out times in the day when traffic has to be routed differently to avoid any one node from being overwhelmed, or may indicate the need for additional nodes in the system, or may indicate the need for a particular node to be updated by increasing its capacity.

Thus the present invention provides a user interface for a telecommunication system load traffic simulator to build up realistic traffic loads by sub-dividing caller traffic load into sub-groups having a common characteristic, whether by time-of-day or by type of call, and by plotting the sub-groups on a timeline that indicates ramp up and decline rates for each sub-group as well as a steady state volume.