Glossary

A code consisting of five characters that represent your company's unique Vendor Code. When you order Sentinel protection keys from Gemalto, You specify your Batch Code, which is then written to the keys before dispatch.

In order to easily identify the batch to which a Sentinel HL key belongs, the Batch Code is written on the outside of each key.

The Batch Code for Sentinel protection keys with a demo Vendor Code is DEMOMA.

The billing data for the Cloud Products included in an Cloud Entitlement. Different type of billing details that you can view are:

• Itemized Billing—A descriptive bill that provides consumption details for a product on per feature per customer basis.
• Detailed Billing—It is less descriptive than the itemized bill and provides consumption details per feature.
• Brief Billing—It provides a brief summary of the products consumed within a specified period.

Specifies how your on-premise application requests and caches licenses from Cloud Connect Server.

• Feature Level — The protected application explicitly requests licenses for individual Features. This type of on-premise licensing is primarily meant for applications running on client machines. The licenses of a particular user are fetched from Cloud Connect and are cached locally. A license request is fulfilled by Run-time either from local cache or by fetching it from Cloud Connect, if the license is not already present in local cache. A license is cached locally either at the time of first request for that license or explicitly when the application detaches the license from Cloud Connect for a specified interval of time. Since licenses for only the requested features are fetched to an on-premise machine based on a user identity, this type of licensing is called as Feature Level licensing
• Entitlement Level— The protected application requests licenses for all the Products/Features at a time in an Entitlement. This type of on-premise licensing is primarily meant for server applications. The protected application is hosted on an on-premise server machine, which is accessed by multiple clients. The Run-time fetches time-limited license slices and caches them locally. The licenses are fetched from Cloud Connect independent of the actual license requests made to Run-time. The Run-time always attempts to serve the individual license requests from the local cache. A license request never triggers a connection to Cloud Connect to fetch a license, even if the license request cannot be fulfilled locally. Since all features of an entitlement are fetched to an on-premise machine, this type of licensing is called Entitlement Level licensing.

A Product that cancels the licensing details of a LDK Product.

A Cancellation Product can be used, for example,

• to revoke a deployed license
• to cancel the license for a Product that has been returned before its license terms have expired

Specifies whether your protected application will be hosted on cloud or will be installed locally.

• Cloud—Your protected application will be hosted on a Cloud Server and the Customers will access the application from Cloud
• On-premise—Your protected application will be installed on the Customer's machine.

A request for items to be shipped to a Customer, specifying one of the following:

• One or more Products to be applied to Sentinel protection keys. The license terms of each Feature in the ordered Products can be specified when the Product is defined, or when the Entitlement is processed.
• A Protection Key Update, specifying changes to be made to the license terms and/or data stored in one or more deployed Sentinel protection keys.

The current status of an Entitlement:

• Draft—The Entitlement is not yet ready to produce. It can be modified or deleted.
• Queued—The Entitlement is ready to produce.
• Product Keys generated—In an Entitlement for one or more Sentinel Product Keys, the Product Keys have been generated.
• Produced—In an Entitlement that includes multiple Product Keys, at least one Product Key has been used to activate the protected software. The Entitlement contains additional Product Keys that have not yet been used.
• Completed—In an Entitlement for updates or for Sentinel HL keys, the entire Entitlement has been produced. In an Entitlement for Product Keys, all the Keys in the Entitlement have been used to activate the protected software. In an Cloud Entitlement, the entire Entitlement has been deployed.
• Acknowledged—Verification has been received that the Entitlement has been applied at the end user site.

Entitlements with status other than Draft cannot be modified or deleted. However, Entitlements with certain status can be reset to Draft. See Reopen.

The way in which the Entitlement items (i.e., Products and Features available with the Entitlement) can be used:

For Sentinel LDK

• Product Key—Associates the Entitlement items to one or more Product Keys.
• Hardware Key—Writes the Entitlement items to one or more Sentinel HL keys.
• Protection Key Update—Enables changes to be made to the license data stored in deployed keys.

For Cloud

• Cloud Unnamed
• Cloud Named

An identifiable functionality of a software application that can be independently controlled by a license. In Sentinel, a Feature may be an entire application, a module or a specific functionality such as Print, Save or Draw.

Features are combined to form Products. License terms are defined for each Feature in a Product.

A period of time during which a user may run software without activation. This allows end users to activate a Product when most convenient for them. During the grace period, and even after activation, end users can pass copies of their purchased software to as many friends as they wish. When a friend installs the software, it automatically reverts to a limited trial version for the entire grace period. After the grace period expires, the software can no longer run until it is activated with a Sentinel protection key.

You can define a grace period for software protected with any Sentinel protection keys. For example, software protected with Sentinel HL keys can be purchased and delivered over the Internet while the Sentinel HL keys are shipped, and end users can start using the software while waiting for the arrival of their hardware key.

To enable a grace period to be specified for a Product, the Product must be defined as Unlocked.

A period of time during which a user may use an expired/exhausted license. The grace period provides an additional time for a user to get the license renewed. You can use the Run-time API, getInfo, to send notifications to users about the grace period. For details of the getinfo API, refer Cloud Run-time Guide.

A task performed by business decision-makers, such as Product or Marketing Managers in an organization. The output of the license planning process is a repository of licensed Products that can be included in customer orders.

Sentinel EMS can be used without a licensing plan.

License terms are defined for each Feature in a Product, and consist of:

• A license type
• A value for the license type
• A value for concurrent use, if relevant
• License accessibility settings

The following license types are available:

• Execution Count—Specifies the maximum number of times the Feature can be used.
• Expiration Date—Specifies the date on which the license expires.
• Perpetual—Specifies that the license is valid for an unlimited period of time.
• Time period—Specifies the number of days until the license expires, from the date of first use.

The license term values for each Feature in a Product can be specified when the Product is defined, or when an order for the Product is processed.

Network licenses that are locked to Sentinel SL keys may also be detachable.

The following license types are available for Cloud Products:

1. Subscription—Specifies that the license to use the product is valid for a specified duration (for example, 3 months, 6 months, 1 year). The product can be used unlimited number of times within the specified duration.

1. Postpaid—Specifies that the license to use the product is valid for a specified duration. The billing can be done based on the usage model, which can either be:
   • Time Based—Billing can be done based on the duration for which the product is used.
   • Count Based—Billing can be done based on the number of times the product is used within the specified period.

Data, such as passwords, values used by the software, unique license terms, software version, site ID, and so on, that is specified in memory when a Product is defined or when an Entitlement is produced. This data is transferred to the Sentinel protection keys when:

• A Sentinel HL key Entitlement for the Product is produced
• A Protection Key Update for the Product is applied
• A Product is activated using a Sentinel SL key

A modified version of another LDK Product containing changes such as:

• A software upgrade
• Extended license terms
• Added or removed Features

For example, a Modification Product can be sent as a Protection Key Update, to an end user who has the original Product and wishes to replace it.

A sellable item that contains one or more Features and/or data defined in memory for secure storage. License terms are defined for each Feature in a Product.

A Product can be from any of the following two types:

• LDK Product
• Cloud Product

LDK Products may belong to one of the following categories:

• Base Products
• Modification Products
• Unlocked Products
• Cancellation Products

Logical partitions within a Batch Code to contain Features and Products.

Product Group has been deprecated from Sentinel EMS 6.3 onwards.

A string generated by Sentinel EMS and supplied to an end user for use as proof of purchase, for the following purposes:

• Product Activation—The end user enters a Product Key that is sent to Sentinel EMS. A Sentinel SL key is sent back and installed on the users computer.
• Update Activation—The end user enters a Product Key that is sent to Sentinel EMS. License updates and extensions are sent back to the connected Sentinel HL key or to the installed Sentinel SL key.

The Product key must be used as supplied by Sentinel EMS without any modification.

The current status of a Product:

• Draft—The Product has been defined but has not yet been included in an Entitlement. It can be edited or deleted.
• Complete—The Product has been included in at least one Entitlement. It is not possible to edit or delete the Product.
• EOL (End of Life)—The Product is no longer available for Entitlements. The Product details are maintained for tracking purposes.

The implementation of an Entitlement. Depending on the type of Entitlement, the production process involves one of the following:

• Burning the ordered Products onto one or more Sentinel HL keys.
• Generating a file containing the Product Keys for the Entitlement.
• Generating a file containing the Protection Key Update for the Entitlement.

The concept of separating engineering and business processes, on which Sentinel is designed.

Engineering processes (software protection) are performed by software engineers using Sentinel protection tools (Sentinel Envelope, Sentinel ToolBox, and the Sentinel Licensing API).

Business processes (licensing and selecting the Sentinel protection key type) are performed by product managers using Sentinel EMS.

Standard Sentinel HL local key that is used to protect software, and has a perpetual license. This key:

• does not have any memory functionality.
• does not support concurrency.
• does not support V-Clock.

Any Sentinel HL key that supports concurrency. This includes the following keys:

• Sentinel HL Net key
• Sentinel HL NetTime key
• Any Sentinel HL (Driverless configuration) key except for Sentinel HL Basic keys

Type of Sentinel HL key that does not require the Run-time Environment in order to protect an application on a Windows machine. These keys provide several advantages over Sentinel HL (HASP configuration) keys:

• (On a Windows machine) Employ HID drivers instead of HASP key drivers. (HID drivers are an integral part of the Windows operating system.) In many cases, it is possible to use these keys without installing any additional support software.
• Support a higher number of Features.
• Provide larger on-key memory space.
• All Driverless keys (except for Basic keys) support a virtual clock for time-based licenses.
• All Driverless keys (except for Basic keys) support concurrency (network-based licenses).

The protection level assigned to a Product when the Sentinel HL locking type is selected. Sentinel HL key protection:

• Offers the strongest enforcement for license terms, which are stored and protected inside the Sentinel HL key.
• Enables portability—the software can be used on any computer to which the Sentinel HL key is connected.
• Does not require Internet connection for activation of the Product.

The software-based protection and licensing component of Sentinel—a virtual Sentinel HL key.

One of the Sentinel protection key types.

The protection level assigned to a Product when the Sentinel SL locking type is selected. With Sentinel SL key protection:

• Product activation is instantaneous. End users can immediately start using the software with its fully-licensed functionality.
• The activation process for end users is convenient and transparent.
• The online connection with end users can enable user registration data to be collected and used for marketing purposes.

Software or data files that can be distributed without a Sentinel protection key for end-user evaluation during a limited time period. See also Unlocked Trialware Product.

Usage type of a Cloud Entitlement. The value can be one of the following:

• Time: Duration of each login session is counted.
• Count: Each login-logout pair is counted as one execution.

This parameter is required for data aggregation and tracking and can be used for billing.

The process by which the end user provides certain information when he logs on to EMS for the first time using Product Key. Behavior of this page differs with the value provided for the User Registration field during Entitlement creation.

• Mandatory—The end user needs to provide some information before he can activate the Product Keys.
• Desired—The User Registration page appears, but the end user can choose to skip this page by clicking Register Later.
• Not Required—The User Registration page does not appear.

A file that contains Protection Key Update data for delivery to end users. This data can include detailed changes to the license terms and/or data to be stored in the end user’s Sentinel protection keys.

The V2C file is generated by Sentinel EMS and can be deployed using RUS or the Sentinel Licensing API. The file name includes an ID, and the date and time it was created.