US
6,219,708
B1
-continued
-continued
32
maXlength=16>
<tr>
Short
Name:
<input
type=teXt
name=short
size=3
maXlength=3>
<tr>
Usage:
<select
name=usage
siZe=1>
5
<th>Date/I‘ime</th>
<option>Inbound
<th>Device</th>
<option>Outbound
<th>Type</th>
<option>Both
<th>User
Id</th>
</select>
<th>Duration</th>
<!——
etc
——>
<th>Phone
Number</th>
<input
type=submit
value=“Set
con?guration”> 1O
</tr>
</pre>
<tr>
</form>
<td>O5-13
13:18:O6</td>
<td>1C</td>
.
<td>Orginate</td>
Analysis
<td></td>
In
one
embodiment,
browser
management
provides
the
15 <td>
user
with
snapshot
views
of
the
system
or
dynamic
updates
it:
list
and
graphs
showing
system
activity.
Analysis
is
available
<td>0543
13:22:O4</td>
in
several
forms,
for
example:
fault/status
reporting,
con-
<td>4C</td>
nection
reporting,
and
usage
graph.
<td>Failed
Security
Check</td>
Fault/Status
Reporting
2O
<hr>
. . .
<tr>
'
As
with
many
SNMP
managers,
reporting
is
an
<t
d>O5_13
13:22:O6</td>
important
management
tool
since
it
informs
the‘
system
<td>6</td>
administrator
as
to
a
problem.
Fault/status
reporting
per-
<td>Device
removed</td>
forms
that
function
under
browser
management.
</tr>
. . . .
t
In
one
embodiment,
fault/status
reporting
is
displayed
as
25
<
r>
_
_ _
<td>O5
13
13.22.11</td>
a
straight
text
HTML
document
or
as a
table.
From
an
<td>7</td>
organizational
standpoint
a table
clearly
shows
the
informa-
<td>DeVice
inSta11ed</td>
IIOII.
</tr>
</table>
3O
<table>
Usage Graph
<tr>
. . . .
<th
colspan=3
align=center>Fauwstatus
EVentS</th>
In
one
embodiment,
device
usage
is
displayed
as a
table
</tr>
showm
ercenta
es
1nd1cat1n
time
connected
verses
idle
g P g g
<tr>
b
. . . . .
roken
down
b
time
intervals
but
this
lacks
the
readabilit
<th>Date/I‘ime</th>
35
y.
,
.
y
<th>DeViCe</th>
of
a
bar
chart,
pie
chart
or
usage
graph.
With
browser
based
<th>MeSSage</th>
management,
charts
and
graphs
may
be used
to
display
usage
information
by
running
Java
applets
that
take
raw
data
<td>O5-13
13:20:53</td>
from
the
communications
device
and
interpret
it
in
a
graph
<td>2B</td>
40
fOrHL
<td>Loss
of
signal</td>
_ _ _
<hr>
The
following
15
HTML
source
code
dynamically
created
<tr>
with
parameters
de?ned
for
the
Java
applet:
<td>O5-13
13:22:O4</td>
<td>4C</td>
<td>Failed
Security
Check</td> 45
</tr>
. . .
<tr>
<t1tle>Dev1ce
Usage</t1tle>
<td>O5-13
13:22:06</td>
<hr>
<td>6</td>
<applet
code=“(-Ihart.class":
width=251
height=125>
<td>DeVice
remOVed</td>
<param
name=t1tle
value=
Device
Usage
>
<hr>
<param
name=columns
value=“4”>
<tr>
5O
<param
name=orientation
value=“horizontal”>
td
0543
13:22:11
td
<param
name=scale
value=“5”>
:td:7</td>
</
>
<param
name=c1ilabel
value=“Idle”>
<td>DeVice
inStaned</td>
<param
name=c1istyle
value=“solid”>
<hr>
<param
name=c1icolor
value=“blue”>
</tab1e>
<param
name=c1fvalue=“20”>
55
<paras
name=c2ilabel
value=“Connected”>
<param
name=c2istyle
value=“solid”>
- -
<
aram
name=c2icolor
value=“
reen”>
Connection
Reporting
p g
_ _ _ _ _ _
<param
name=c2ivalue=“65”>
'
In
one
embodiment,
connection
reporting
is
very
similar
<param
name=c3ilabel
Value/4005”>
1n
method
as
to
how
fault/status
reporting
is
performed.
The
<param
name=c3istyle
value=“solid”>
information
related
to
each
connection
active
in
the
system
60
<Pamm
name=c3icolor
Va1ue=“Ye11OW”>
ma
be
dis
la
ed
in
a table
<param
name=C3*Va1ue=“1O”>
y p y
'
<param
name=c4ilabel
value=“Faulty”>
<param
name=c4istyle
value=“solid”>
<param
name=c4icolor
value=“magenta”>
<param
name=c4ivalue=“5”>
<table>
</applet>
<tr>
65
<hr>
<th
colspan=6
align=center>Connection
Information</th>
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales