User Manual

imageWARE Remote – Technology Whitepaper Canon U.S.A., Inc., All rights reserved.
9
process).
• Error/jam/alarm notifications can be sent directly to the service provider by e-mail upon
occurrence (push process).
• The service provider can also log onto UGW to obtain information on any error/jam/alarm
notification (pull process).
4. eRDS Network Security
LAN
Communication Target and Protocol
The eRDS communicates only with the UGW and is unable to communicate
with other devices that are connected to a customer’s Local Area Network.
Communication
between UGW
Server and
eRDS Devices
Communication Target
The eRDS enabled imageRUNNER communicates only with the UGW when
sending device information. The authentication method is described later.
Communication Protocol
The eRDS enabled imageRUNNER communicates with the UGW by using the
HTTPS protocol. The eRDS enabled imageRUNNER acts as the “Client”, and
will never become a HTTP server for the purposes of eRDS communication.
Please note that some imageRUNNERs may act as a HTTP server for other
non-eRDS related features.
Data to be collected and forwarded
The data to be collected by eRDS and forwarded to UGW is shown in Table 1.
The eRDS enabled imageRUNNER sends the data shown in Table 1 to the
UGW at the specified timing.
In the “regular counter transmission”, the maximum size of the transmitted
data package is about 250 KB. This transmission occurs only once every 16
hours.
Table 1
Data to be sent Description Timing to send Amount of data
Error data Includes the error code, error
subcode, date of occurrence, total
counter at occurrence, paper
feeding slot, and paper size.
When an error
occurs
4 KB