IEEE Technology and Society Magazine - Fall 2014 - 50

Data

Client APIs (Private)

TCF/TCC Owner
with Devices

(2)
Policy
Store

Policy Component
(3)

Rule Engine
Component

Personal Data
and Attributes

(2)
ID
Mgmt
Tool

Registry

Trusted Compute Cell

Identity/Persona
Component
(4)
(5)
Applications
and Registry Applications
Management Execution
Server
Applications and Compute
Management Component

App. Access APIs

(1)

Identity
Server (IdP)

Identity APIs

Manage

(2)

Data Access APIs

Policy
Mgmt
Tool

Big Data
Corp

Identity Providers
and Relying Parties

User
(via their TCC)

Trusted Compute Framework
Fig. 2. Functions of the TCC.

shared applications management,
and other group-supporting services.
The OMS project designed the
TCC as a cell unit from which larger
digital "organisms" and social constructs can be created in network
spaces. To perform these functions,

Personal Data Store (PDS) Management: The PDS system is a component inside the TCC that collects
data (or receives streams of data)
coming from the owner's devices,
either generated by the device (e.g.,
GPS data) or proxied by the device

We need a network architecture
and software systems that can
facilitate the formation of trust
and social capital in user-centric
and scalable ways.
the TCC must fulfil five distinct
technological functions, as illustrated in Fig. 2:
Identity Management: The function of identity management includes
authentication, authorization, audit
and log, core-identity and persona
management, group identity management, assertions and claims management, single-sign-on (SSO) establishment, and more [2].
50

(e.g., device pulling down copies
of the owner's postings on external
social network sites). The PDS system also exposes a number of APIs
to external readers or consumers
of the de-personalized data, such
as analytics organizations and data
brokers that make the de-personalized data available to the market.
An important sub-component of
the PDS system is the dynamic rule
engine, which performs the role of a

filtering gateway for access requests
to the TCC owner's data in the PDS.
Applications Management: Applications within the OMS architecture
will be executed in the context of the
calling (and managing) TCC. The
owner of a TCC can stand-up an
application for his or her sole use, or
stand-up an application that will be
shared by a group or community. A
shared application can then be made
accessible (to other TCCs who are
community members) through its
published APIs. As such, the management and instrumentation of
applications is a core requirement
of TCCs.
Compute Power Management:
Related to applications management
is the need for compute power to be
expanded or reduced in an elastic
manner depending on the current
demand of the TCC. Elastic compute
capability is particularly relevant in
the case of community-shared applications, which may be shared by
hundreds to millions of TCCs.
Registry and Cell Management: The registry in the TCC is the

IEEE TECHNOLOGY AND SOCIETY MAGAZINE

FALL 2014

Table of Contents for the Digital Edition of IEEE Technology and Society Magazine - Fall 2014