Identity & Context - Coming Soon

Contextual Composition of Converged Services

By Rakesh Radhakrishnan, Abbie Barbir, Ph.D and Mark Dixon

Overview

In this sequel to the series of books on Identity (Identity & Security, Identity & Policy, Identity & Context), the authors, explore and explain how an Identity System, with its federation model, can act as a conduit that carries context in the network (between multiple service networks, content networks and multi-media networks) so that composition and choreography of converged services can take place with the appropriate context.

Every connection and every call made via the network is for a reason and within a context; the reasons can range from getting information, conversing with a group, invoking services, responding to an event and consuming services. One amongst the core value proposition of an Identity System for an Enterprise SOA Network and a Telecom Carrier's SDP Network is the notion of "Contextual Composition of Converged Services" - Context STARTS with a User (and his/her identity) and a sub-context;


  • Task or Enterprise Context (user’s activity/activities as an employee, doctor, citizen, etc.)
  • Social Context (friends, family, mentor, coach, redskin fan, etc.)
  • Personal (physical and mental attributes about a user)
  • Spatial-Temporal or Mobility Context (attributes such as time, location, movement, calendar, etc.)
  • Environmental Context (users surrounding - including entities, such as others, devices, etc.)

Identity & Context
Contextual Composition
of Converged Services
By Rakesh Radhakrishnan,
Abbie Barbir, Ph.D and Mark Dixony

COMING SOON

Here an Identity System adds value by gluing together all relevant contextual attributes to an identity after a User Authenticates with a Authentication Authority and all relevant Attributes are retrieved from the respective -context- Attribute Authority after abiding to the respective domains policy requirements. The "Contextual Composition" however adds another dimension - Composition of the relevant service and content for a user is accomplished after the contextual attributes are FED within a session. BY Fed (we mean both feeding the data and federating the contextual data from multiple sources). The idea again is that composition and choreography is preceded with context all the time. Converged Services, implies Voice, Data and Video Service Building Blocks delivered as one Application. The KILLER APP is the Contextual CALL to the Network. Every Call you make is within a context; and composes multi-media services; A Call made to a friend, a call made with fellow employees, a call made to your doctor, and more, and every Call is not just a Voice CALL - It’s a Multi-Media Converged Application Call.

  • the call to the friend automatically loads the relevant context (your joint trip pictures, topic of your last call, your group buddies -common to you and the friend, any planned joint events and more),
  • the call to your fellow employees automatically loads the group collaboration site, agenda for the call, the brief bios and pictures of the participants, the areas of specialization and participation of the team members and more),
  • the call to your doctor automatically loads the medical transcripts, recent visit data, current medications taken, pending questions to ask and more).
Therefore Identity Enabled, Policy Based, Context Aware - Composition of Federated Content and Services will be the reason why the Carriers (Cable, FIOS, 4G, and more) exist. As they leverage the Network and its Intelligence of the Users/Subscribers for the Delivery of Cohesive and Convenient Contextual Services, what is also referenced by Sun Microsystems as “Project Destination”.

The core value proposition of "Identity enabled SOA" is the notion of carrying context securely (ranging from authentication context, to authorization context and other contextual data) which essentially highlights the importance of Federation for Mobile Operators from a Attribute exchange standpoint and how that adds value when fusing multiple service types (multi-media, business, social services and more). This is the topic of this book that covers the IDEA (identity enabled architecture) behind how Federation lays the Foundation for Fusion; from many perspectives;

Without Federation Technologies none of the fusion frameworks will be possible. There are many types of IDP's (identity service providers) and PDP's (policy decision points) for business enterprises however the Mobile Operators IDP and PDP has a special unique value proposition to offer mobile consumers, that cannot be true with other environments (making mobility the macro context), especially with the roll out of 4G (2010-2013) and 5G (2014 and beyond) networks. In fact from an Operators perspective Digital Identity is nothing but a “Construct of Credentials for a given Context”. The 1st book “Identity and Security” discussed vertical and horizontal integration of Identity Systems from an Authentication Authority perspective, and the 2nd book “Identity and Policy” discussed a pervasive policy paradigm, with orchestra table policies of an Identity System from a Authorization Authority perspective. This book on “Identity and Context” discusses the relevance of an Identity System as an Attribute Authority, which can exchange attributes about identities and entities securely.

 

 

About the authors

Rakesh Radhakrishnan is the Chief Identity Integration Architect and Lead Technologist in the Communications Market Area of Sun. He has covered Telecom Companies, Network Equipment Providers (NEP), Independent Software Vendors (ISV) and Service Provider accounts in Europe, Canada, USA and Latin America. He has over 15 years of experience and has an MBA (MIS) and MS (MIT). He is also the FAM Product Lead for the Software Sales Organization, in Sun. He is an active member of Customer Engineering Council (CEC) and was the Chairman of a Working Group on Container Alignment Engine (CAE patent received from Europe and US) and the patent on STAR. He also has Defensive Disclosures on Correlated Identity.
 

 
He has published more than 50 papers on IT Architectures (Frameworks, Process and Techniques) and is a frequent speaker at conferences and events including IDTrust, ITU, DIDW, OMG, TOG, CMG, IRM, SuperG, SunNetwork, Java ONE, Stanford University and Oxford University, etc. He has led multiple Architecture Workshops and Architecture Assessments for IT Consolidation and Network Identity projects. He was recently featured on Officer Outlook for his work on Aligning Architectural Approaches (Sun's WS-Incite Award for 2005). He is the recipient of the "Above and Beyond" award from the Sun/Nortel team in 2007 and also the "Outstanding Contributor Award" from SEI. He was selected as a "Stellar Volunteer" -amongst 25 such volunteers from Sun Celebrating 25 years.


Rakesh is also certified by The Open Group (on TOGAF 8), SEI (as a SW Architect) and OGC (Prince 2 and ITIL). He has Green Belt Six Sigma training. He is a ECCSE (Enterprise Computing Certified Systems Engineer -Competency 2000- from Sun) and a Systems Architect Pro (from Peoplesoft). He is the Author of the Book titled "Identity and Security" and its sequel "Identity and Policy" (2008). His blog can be found at http://www.network-identity.com

 

Abbie Barbir, Ph.D., (abbieb@nortel.com) is a member of Nortel's Strategic Standards group, where he serves as Senior Advisor in the areas of Web services and Security. This role has involved him in many activities within OASIS, W3C, WS-I, OMA, ITU-T, Canadian Advisory Committee (CAC) JTC1 SC6, IETF, Parlay and IPSphere. He currently chairs the Cybersecurity question in ITU-T SG17 and is the vice chair of the CAC for JTC1 SC 6. In 2005, he represented OASIS to ITU-T and was instrumental in having the ITU-T consent the SAML and XACML OASIS Standards as ITU-T Recommendations. Abbie holds a Ph.D. in Computer Engineering from Louisiana State University in Baton Rouge, USA. In his more than 20 years in the software and telecommunication industry, he has been a professor of Computer Science in Western Carolina University, an application developer, data compression and encryption inventor, systems architect, security architect, engineering manager, consultant, author, and inventor of numerous security algorithms. His term on the TAB extends to July 2010.


 

Mark Dixon currently serves as Chief Identity Solution Architect, North America Software Line of Business, Sun Microsystems. A well-known thought leader in the Digital Identity Management market, Mark publishes a popular blog, Discovering Identity, regularly exploring how Identity Management principles and technology can enable innovative business practices. He joined Sun in 2004 as Practice Lead in Sun's Identity Management Practice and subsequently served as Systems Engineering Manager for the Telecommunications Market Area in Sun's US Software Practice. He was formerly CEO of two software startups and senior practice director with Oracle Telecommunications Consulting Services. A graduate of Brigham Young University, Mark and his wife make their home in Mesa, Arizona.

Blog: “Discovering Identity”: http://blogs.sun.com/identity
 
© futuretext® Ltd 2005 Web Design by Perfect Blue