Detailed Description

The storage feature enables ISV applications to allocate and use Non-Volatile Memory (NVM) that Intel AMT manages locally on the client platform. Data placed in an NVM memory block are persistent. As a result, this data can be accessed even while the Operating System (OS) is not functioning or is uninstalled, as long as the system is physically connected to power and to a network.

Intel AMT maintains the NVM. ISV applications can use Intel AMT to allocate, maintain, and specify access to the NVM. Both local applications (such as a local ISV agent) and remote ISV applications (such as a remote console application) can access and update stored data in the NVM. Also, multiple applications from the same vendor can share stored data in the NVM. The total size of the NVM depends upon the specific implementation, but must be at least 96KB, and is always a multiple of 4KB.

ISV storage in the NVM is divided into two areas: Partner storage and Non-Partner storage. Partner storage is pre-allocated in the Intel AMT firmware. The amount of storage available to a specific application is limited by the amount allocated to it in the Factory Partner Allocation Control List (FPACL) and by the total amount available to Partner and Non-Partner applications. The sum of memory allocated to all Partner allocations is greater than the amount actually available to the applications – the partner space is “overbooked” based on the assumption that a single enterprise will not deploy every possible ISV application. You can use Storage Administration methods to change the value allocated to different applications.

Non-Partner applications are those that are not listed in the FPACL. Storage can only be allocated to Non-Partner applications from the Non-Partner area of the NVM.

The Enterprise Access Control List (EACL) lists enterprises that are allowed to register applications. The Storage Administration service enables you to add enterprises to the EACL. The Storage service enables enterprises listed in the EACL to register applications.

Two interfaces to storage (provided as CIM classes) provide two different kinds of services. The storage administration interface provides management of the FPACL and the EACL lists, including the ability to add and remove enterprises and applications. The storage interface is used directly by applications for performing storage operations.

The two interfaces (storage admin and storage) serve different purposes. A good analogy is the distinction between a database administrator and a database user. The administrator creates and manages users and allocates resources to them.  A user simply uses his resources, and with permission, accesses the resources of other users. The same applies to 3PDS.

Beginning with Release 6.1, a local user can perform Storage Administration.

See Also:

   Storage Concepts and Objects

   Application Development Guidelines

   Examples of Using the Storage Feature

Copyright © 2006-2022, Intel Corporation. All rights reserved.