Cisco Technology, Inc.

Oracle International Corporation

Sachin Agarwal

Chih-Tsung Huang

Wei-Jen Huang

Chirag Shroff

Sha Ma

Srirajkumar Sundararaman

Samir Valjibhai Rajgor

Aviran Kadosh

Dylan Thomas Walker

Joan C Teng

Thomas B Remahl

Michele C Lee

Lakshmi Velandai Thiyagarajan

Srinivas Vundru

Kevin Shyh-Kang Chang

Tatiana Serguei Dorofeeva

Elise Y Tung Loo

Chi Cheng Lee

A method for monitoring an Integrated Circuit (IC). The method includes a Root-Of-Trust (ROT) module to actuate a monitoring process to monitor at least one feature being performed in ongoing operations of the IC in accordance with a policy. The ROT module receives data that defines the policy that includes at least one feature being performed. A validating process is applied by the ROT module to data by using firmware and by using at least one built-in key of a plurality of built-in keys retrieved from a secure storage. The ROT module determines whether at least one feature is being performed in the ongoing operations of the IC in compliance with the policy. The ROT module applies an impairing process to impair at least one feature of the plurality of features being performed to attempt to place the performance of the ongoing operations of the IC in compliance with the policy.

Using root-of-trust (ROT) to continuously monitor device operation for impairment

A method of operating a system-on-chip (SOC) including decrypting, by isolated Root of Trust (RoT) code, a Stock Keeping Unit (SKU) license code from a host during bootup of a device. Then validating, by the isolated RoT code, the SKU license code with firmware and at least one built-in key of a plurality of built-in keys from secure storage. Finally, enabling or disabling, by the isolated RoT code, at least one feature set of a plurality of feature sets comprising resources configured at the SOC based on at least one SKU license code which has been decrypted by isolated RoT code using at least one built-in key and authenticated by firmware.

On-demand and secure hardware license-based SKU creation for ASICs

Techniques are described for a memory device. In various embodiments, a scheduler/controller is configured to manage data as it read to or written from a memory. A memory is partitioned into a group of sub-blocks, a parity block is associated with the sub-blocks, and the sub-blocks are accessed to read data as needed. A pending write buffer is added to a group of memory sub-blocks. Such a buffer may be sized to be equal to the group of memory sub-blocks. The pending write buffer handles collisions for write accesses to the same block.

Performing multiple write operations to a memory using a pending write queue/cache

Technology is disclosed for supporting the use of multiple access mechanisms for accessing one or more data stores. Examples of access mechanisms include the LDAP protocol and the ADSI protocol. One embodiment of the present invention includes maintaining an association of access mechanisms to types of data store operations such that two or more types of data store operations for a first data store can be associated with different access mechanisms. The system receives a first operation for the first data store, where the first operation is of a first type of data store operation. The system accesses the first data store to perform the first operation using an access mechanism associated with the first type of data store operation.

Support for multiple mechanisms for accessing data stores

Technology is disclosed for automatically configuring attribute sets, such as object classes and classes of database tables. A system employing an object class, such as an Identity or Access System, configures the object class for use by the system. One version of the system employs a template that includes entries for attributes in the object class. An example entry identifies an attribute and a corresponding meta-attribute. Alternatively, the template may support multiple object classes and include entries with different types of information. During configuration, the system selects an attribute in the object class and identifies a corresponding template entry. The system configures the attribute, based on the information in the template entry. One type of configuration includes the system assigning a meta-attribute from the template entry to the attribute. The system repeats this procedure for each attribute in the object class or at least a subset of the attributes that need configuration.

Automatic configuration of attribute sets

Identity Servers issue and respond to requests for performing remote operations. A local Identity Server receives a request to perform a remote operation. The local Identity Server identifies and executes any required local operations. After completing the local operations, the local Identity Server forwards the remote request to a remote Identity Server, which executes the remote operation. An Identity Server includes a management service, management registry, and request handler. The management service identifies and issues remote request to other servers. The request handler receives remote requests from other servers. The management registry maintains an index of function modules for performing local operations.

Blocking cache flush requests until completing current pending requests in a local server and remote server

Technology is disclosed for limiting the number of central data store accesses required when performing a series of steps, such as a workflow. A local data store is coupled between a central data store and a system carrying out a workflow. Alternatively, a Transfer Engine is coupled between the local data store and the central data store to transfer data between the local data store and central data store. The Transfer Engine allows the data formats in the central data store and local data store to be independent of each other. During a workflow step, the system stores attributes related to the workflow in the local data store&#x2014;updating modified attribute values and creating entries for newly added attributes. The system determines whether any attributes in the central data store need to be updated with attribute information from the local data store. The system only updates the central data store with local data store attribute values for new and modified attributes when necessary&#x2014;avoiding central data store updates after every workflow step.

Growing community of inventors

Sunnyvale, CA, United States of America

Sachin Agarwal