[Cloud] Minutes posted from today's Cloud Imaging WG conferencecall

[Cloud] Minutes posted from today's Cloud Imaging WG conferencecall

[Cloud] Minutes posted from today's Cloud Imaging WG conferencecall

Petrie, Glen glen.petrie at eitc.epson.com
Mon Jul 22 17:06:48 UTC 2013


Bill,

 

I have not read other's responses yet, but this is how I see things. 

 

Glen

 

 

________________________________

As I generate a Registration section for the Cloud Imaging Model, I
would like to verify my understanding of the decisions made at Monday's
meeting.

 

1.    The A Cloud Solution registered Device Owner, operates ing through
a Cloud Client Device Management Application, which communicates with
the Device's Cloud Imaging Device Proxy which in turn communicates with
the Cloud Solution to provide for device and device services
registration. that provides the cloud interface for the device,
registers the device and the device services he wishes to make available
to the Cloud Imaging System. Note that individual device elements,
attitudes, objects and services may have selectable access capability
for each Cloud Solution Registered User of the device.  He may desire to
block access to specific Device elements and Service elements. The Cloud
Client Device Management Application (CCDMA), on behalf of the Cloud
Solution registered Device Owner and again communicating through the
Device's Cloud Imaging Proxy (DCIP), request In response to information
provided by the Device owner to the Proxy:

a.    the DCIP to initiates a device registration request to the Cloud
Solution for the Cloud Solution Registered Device Owner.  

1.    The DCIP establishes, with the Cloud Solution, a communication
protocol and security mechanism for further interactions.

For Bi-Directional Communication (all requests/tasks are communicated
with the CCDMA)

1.    The Cloud Solution request the basic (root) information for the
device (example: 1284.4 information). 

2.    The Cloud Solution request the "available" device capabilities;
such as, elements, attitudes, objects and services that the owner
identified using the CCMDA.

3.    [Optionally] The Cloud Solution requests the current status and
state of the device being registered.

4.    Device is now registered and bi-directional communication is
maintained.

For Uni-Directional Communication (all requests/tasks are communicated
with the CCDMA)

5.    The DCIP makes a request to the Cloud Solution to send basic
(root) information for the device (example: 1284.4 information). 

6.    The DCIP makes a request to the Cloud Solution to send "available"
device capabilities; such as, elements, attitudes, objects and services
that the owner identified using the CCMDA.

7.    [Optionally] The DCIP makes a request to the Cloud Solution to
send the current status and state of the device being registered.

8.    Device now registered and polling will be used to check on
available jobs. 

2.    proxy provides Device registration information with an initial
Update System Elements message to the Cloud System Control Service. This
message provides information on all System Elements of the Device that
are to be made known to the Cloud Imaging System. It corresponds to a
response to a current Get System Elements message with all elements
identified.

b.    The Proxy identifies the Device Services that are to be accessible
to the Cloud Imaging System by sending an Identify Services message to
the Cloud System Control Service. This corresponds to a response to a
current List Services operation.

c.    The proxy identifies the elements of each Device Imaging Service
that are to be made available to the corresponding Cloud Imaging Service
by sending an initial Update Service Elements to an Owner-identified
corresponding imaging service of the target Cloud Imaging System. This
corresponds to a response to a current Get Service Elements operation.

2.    Once Device and Service registrations are complete, the Proxy will
maintain contact with the Cloud System Control Service and the
registered Imaging services, updating System and Service Elements and
checking Cloud Imaging Services for jobs.

Note: 

1.    It was decided that:

a.    Devices and Service are registered, not subunits

b.    Device Services can only be registered with a corresponding Cloud
Imaging Services with in the Cloud Solution. 

c.    Therefore: a Device subunit cannot be made accessible to a Cloud
Imaging Service unless that subunit is configured as part of a Device
Imaging Service that is registered with the Cloud Imaging Service. For
example, a Cloud FaxIn Service can not use a marking engine in a Print
Device unless that marking engine is also configured as part of a FaxIn
service that is registered with the Cloud FaxIn Service. (This seems an
unfortunate limitation to me.)

2.    It was agreed that the Owner will want to place restrictions on:

a.    Which Cloud Solution Registered Users Who can use the device, with
respect to one or more of the following:

                                                          i.      User
ID, possibly including results of authentication 

                                                      ii.
Geographical or network typological origin of the user

                                                  iii.      Payment or
credit 

                                                      iv.      Any one
of various other conditions (time, loading, .....)

b.    What services a Cloud Solution Registered Users user can use

c.    When each Cloud Solution Registered Users user can use what
services (e.g., Print and Hardcopy Fax and Email only during working
hours; FaxIn, EmailIn to storage all the time)

d.    Degree of use (e.g., max number of copies)for each particular
Cloud Solution Registered Users user and Service

e.    Probably other conditions

The Cloud Solution Registered Device Owner owner will communicate with
the Cloud Solution Cloud Imaging System with an "access list" to
identify these Cloud Solution Registered User access rights and
restrictions to individual Cloud Imaging Service. This process is out of
scope for the Cloud Imaging Model.

 

I would appreciate confirmation or correction of this understanding.

Thanks,

Bill Wagner

 

 

-----Original Message-----
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
Michael Sweet
Sent: Monday, July 15, 2013 4:25 PM
To: cloud at pwg.org
Subject: [Cloud] Minutes posted from today's Cloud Imaging WG conference
call

 

All,

 

I have posted the minutes to today's Cloud Imaging WG conference call
to:

 

 
ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20130715.p
df
<ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20130715.
pdf> 

 

Our next conference call will be on July 29, 2013 at 3pm ET.

 

_________________________________________________________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 

 

--

This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.

 

_______________________________________________

cloud mailing list

cloud at pwg.org <mailto:cloud at pwg.org> 

https://www.pwg.org/mailman/listinfo/cloud
<https://www.pwg.org/mailman/listinfo/cloud> 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner <http://www.mailscanner.info/> , and is

believed to be clean. 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20130722/b64eee48/attachment-0002.html>


More information about the cloud mailing list