Page 592 - Cloud computing: From paradigm to operation

3 XaaS

– identifies the user profile managed by the user profile management function (see clause 7.3.2) if a
DaaS user has already been registered;
– coordinates with different virtualization infrastructures according to a delivery protocol, in some
cases the client connection needs to be customized according to dedicated infrastructure;
– sends virtual desktop access information and/or other formats like a customized access connector
software, access connection plugins in a browser to a DaaS client to proceed with client connection;
– performs connection monitoring for any type and reconnection with the connection monitoring if a
DaaS client is disconnected; it also guarantees both security and quality of service (QoS) of the
delivered DaaS service based on the connection;
– validates the license of the user's applications of virtual desktops.

7.2.3 User access management

The user access management function:
– validates a DaaS user with CSU's access information in logon procedure;
NOTE 1 – CSU's access information is registered at the portal of a DaaS platform or a DaaS user's terminal. This
information includes ID, password, and other check items for authority. This information can be used in login
procedure.
NOTE 2 – For a DaaS user who accesses DaaS for the first time, an administrator prepares CSU's access
information for the DaaS user's logon procedure in advance in the user account and profile management
function (see clause 7.3.2).
– accesses the user account and profile management function (see clause 7.3.2) for each DaaS client
according to CSC types, the information may be used to authorize access, establish connections with
DaaS-specific protocol/connection;
– notifies the result of a client connection to a DaaS client to give guides to access a DaaS platform
and requests the client connection to the client connection management function (see clause 7.2.2)
after validating a DaaS user, the access can be achieved through a dedicated connector software or
through a web browser and plugin supporting DaaS-specific protocol;
– supports differentiated permissions according to CSC types;
NOTE 3 – The permissions are classified into authority of administration, resource access, and service access.
– supports secure access through a security protocol (such as secure shell or transport layer security)
and technical access depending on the type of DaaS client such as the dedicated software, general-
purpose web browser;

– maintains logs such as the date and time of the user log-on and log-off, the type of DaaS client, the
location of the DaaS client, and the service usage, etc.

7.2.4 Provisioning and allocation of virtual desktop
The provisioning and allocation function:

– prepares hardware and software resources for a virtual desktop corresponding with CSU's account
information, load-balancing or allocation policy;
– configures a DaaS platform with a virtual desktop delivery protocol and resource pool for virtual
desktop environments;
NOTE 1 – This function involves the following processes:
• the provision for a DaaS client configured to receive the allocation of a virtual desktop;

• the provision for a connection manager to control a type of a virtual desktop to be allocated
according to CSU's account and access information;
• the provision for a DaaS Platform to be selected among platforms in the datacentre or server
farm on which the virtual desktop is allocated.

584