Browse Prior Art Database

Conditional Trace for Play back

IP.com Disclosure Number: IPCOM000199608D
Publication Date: 2010-Sep-13
Document File: 6 page(s) / 187K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for playing back communication traces and to provide a mechanism for users to merge and edit communication traces to one conditional trace.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 39% of the total text.

Page 1 of 6

Conditional Trace for Play back

1. Background:

a. Communication Trace - In terminal emulation software, the communication trace feature offers the capability to record the network traffic between the server and the client machine. The recorded trace can be saved and be played as a live connection. The communication trace is often used for demo purpose, problem recreation and software testing, etc.
b. Drawbacks of Present Arts : The challenge for the capability of the communication trace file recently is:
b.1 The communication trace file contains frames recorded for only one route which is unique to a particular scenario. It means that the user will need to record down numbers of communication trace files for different user scenarios even thought the most of frames and user inputs in communication trace files are redundant. For problem determination purpose, it might be acceptable. For demo/software testing purpose, maintaining a mount of communication trace files will be a burden.
b.2 When reproducing different user scenarios, the user needs to go through all frames (frame, web page) recorded until target frame appears. It takes time and it is unnecessary.
b.3 Communication trace files can not be merged into one. If communication trace files include the same frame in it, users can not easily merge those files into one file so that different routes could be merged as one directional graph.
b.4 The communication trace can not emulate how the product interact with the user.
b.5 No visual tool to make editing frame data easily.
c. In current trace record and playback mode, users do not have chance to see different results in one communication trace, since traditional communication trace is one by one frame for emulator to playback. The core of this invention is to present the idea of "conditional trace", and to provide a mechanism for users to merge and edit communication traces to one conditional trace. The one traditional communication trace will become a trace of directional graph, and decision points of the branches are conditional.
2. Description of Invention:

a. Key Idea and Claim:
a.1 Traditionally, the communication trace is always "linear" one - it doesn't support branch from frame to frame.The idea of "conditional" trace is the next frame to be shown depends on the command give by the user in current frame.
a.2 How to merge linear trace to conditional one and the ability to edit the trace are also presented.
b. Example: Here are 2 examples of user scenarios:
b.1 Live Mode - create the conditional trace by recording the live

communication trace:

  A user wishes to record traces to demo different frames in a host. Different frames will be presented with different input of command in one specific frame 'F1'. That user start recording by click "record" button, the trace tool records the trace from start frame to the frame 'F1', and then set this frame as a decision point. Then the user inputs 'A' command into command line of the frame "F1"...