Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Enabling Identity Usage Tracking within DSN Memory

IP.com Disclosure Number: IPCOM000249458D
Publication Date: 2017-Feb-27
Document File: 2 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database


Disclosed is a method is to enable identity usage tracking within Data Source Name (DSN) memory in order to provide granular usage tracking information.

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


Enabling Identity Usage Tracking within DSN Memory

Data Source Name (DSN) memory calculates and stores usage information regarding source data that it stores and does so for collections of data (e.g., container or storage account). Examples of such usage could include data usage (e.g., bytes stored, number of source data entities), operational usage (e.g., number of operational requests), and traffic usage (e.g., throughput consumed). Such usage information is used for introspection, quota enforcement, and billing.

For circumstances in which a number of identities (e.g., individual users or deployed services) share collections and utilize data, it is desirable to have granular usage tracking information regarding what identities are contributing to the usage of source data and to what degree. As a data usage example:

 A storage account within a DSN memory stores 50 petabytes (PB) of data  Usage information records 50 PB as used storage within that account  This account is utilized and shared across user #1, user #2, and service #1  Identity usage shows that user #1 is consuming 10 PB of that data, while user #2

is also consuming 10 PB, while the service #1 is consuming the remaining 30 PB of data

The novel method is to enable identity usage tracking within DSN memory. The implementation steps follow.

For all source data requests: 1. The ds processing unit determines the identity of the requester (e.g., an end user

or a deployed service/application) as part of existing authentication and access control logic. This could occur via user supplied token, credential, centralized identity management interactions, or network address. For this example, the assumption is that the requester has been authenticated and authorized to store source data.

2. The ds processing unit examines the various forms of identity usage information for the storage collection of the source data (e.g., container or storage account)

During a request to store source data: 1. For operational and traffic usage:

A. The ds processing unit updates operational usage base...