subscribe

1
Issue on Reducing Events Analysis of Event Model
The alleviation method for too much notification
is, - Less destinations - Less frequency - DPWS
must define the alleviation method.
create subscription object with in the memory
system. it can destroy unsubscribe operation.
subscribe
Persistence(option) to store it during
power-recycle
notification
event queue
HDD/NVRAM
to check the target is down, needs waiting the
timeout.take too much time to deliver events.
(30-75sec. common value for printer products)
down
high frequency
too many threads and sockets
the cost is high for network and device
manydestination
2
Issue on Reducing Events Contrib. 1 Request
Driven Type The purpose is to decrease the
number of notification destinations in event
processing requested by outside.
no event recipient information(URL)
within WS-Eventing spec.
target PC
subscribe()
Reducing the destination number needs the
relationship information of subscription object
within device and job events. Job is not printer
unique object, is for all of embedded devices
others
filtering
job completed(high frequency)
note - HP officeject J6400 31ppm(33msec/job-comple
ted event) even 150 MFD!!
too many PCs to send the job events
3
Issue on Reducing Events Contrib. 2 Severity
for static information Type The purpose is to
decrease the frequency of notification. MIB
Severity is a good concept for achievement the
purpose. In addition, there is an advantage that
device can correspond the MIB system.