Browse Prior Art Database

Method and System for a flexible, Policy Based, approach to implement Trial SW Versions in a SaaS environment

IP.com Disclosure Number: IPCOM000238511D
Publication Date: 2014-Sep-01
Document File: 3 page(s) / 442K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes a way to distribute and manage licenses on a Software as a Service (SaaS) environment, where license types are dependent on the usage data and other parameters typical of SaaS software.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Method and System for a flexible , Policy Based , approach to implement Trial SW Versions in a SaaS environment

    Typically every software product offers an evaluation period to its customers. The way it is implemented is a given period to try its usage (i.e. 30 days) or a limit the number of functions or limiting the installation. Anyway there are some drawbacks. In fact, this static way of managing the trial period doesn't take into account the fact that a customer could have decided to use it in an intermittent way (so 30 days are meaningless).

    Also, in a SaaS offering, providing such a disconnected and not customizable function cannot be appreciated by customers, who would like to test the product and then switch without doing anything on their side, because of the connectivity to the cloud.

    Another parameter is that, the cloud should be smart enough to "understand" and "tune" what should be really the payload of the product and limit the evaluation to that portion of the software. For example, a tool used to download content should be limited to how much the customer can download a tool used to monitor resources into the enterprise should be limited to power of machines or number of endpoint managed and so on.

    The idea here disclosed is to monitor every customer using the cloud and release evaluation usage or normal usage to them depending on their requests (and payment). Also depending on the type of software requested, the kind of evaluation is different and is centrally managed by the cloud itself. Now new options are possible for both the customer and the owner of software/cloud:

      - the customer can decide to suspend the evaluation and to pass to normal usage without installing/migrating

    - the customer be measured for the real payload of its software and can forget to hurry up in testing his environment (because the license is expiring)

      - an agreement, between customer and cloud, is possible about when and how to manage the evaluation period

- it will be not possible to circumvent the evaluation rules

Basically the evaluation policy will depends on these parameters:

- the customer
- the product (the specific rules for the product)
- the current usage of that product done by that customer

1


Page 02 of 3

This can in obtained with the following...