Jeremy Mazner Program Manager Microsoft Corporation BB35.
-
Upload
christina-noyes -
Category
Documents
-
view
225 -
download
2
Transcript of Jeremy Mazner Program Manager Microsoft Corporation BB35.
Live Services: The Future Of the Device Mesh
Jeremy MaznerProgram ManagerMicrosoft Corporation
BB35
Mes
h Se
rvic
es
Identity Directory Storage Communications and Presence
Search & Geospatial
Users Devices SynchronizationApplications
Live Services
Device Scenarios
creator
creator
consumer
processorconsumer
rich end-point
Device Platform Experience
demo
Device paradigm
App paradigm
A device might need to Determine what’s changed in a folder Update contents of a folder Subscribe to real-time notifications Publish transient or persistent properties Communicate with other devices
And present itself to the user as A separate application or service that
interacts with all Mesh content A device in the Device Ring that can be
configured per folder
Interacting With Mesh Services
App paradigm
Device paradigm
A Tale Of Two Paradigms
Application DeviceRegistered device
No Yes
Authorization Delegated Device mappingUser experience
Custom app Platform experience
Device horsepower
Low Medium to High
Delegated Authorization (Simplified)
This user wants to authorize me
Yes indeed!
Here’s your token
Do you really want to authorize this app?
appapp
I want to use this app
See alsoBB22 Identity: Live Identity Services DrilldownBB30 Live Services: Building Mesh-Enabled Web Applications…
What Defines A Mesh Device?
Queue Service
Device Connectivity
ServiceDirectory Service Storage Service
MeshObject
MeshObject
MeshObject
DeviceID
Notifications Transient properties
Persistent properties
Device mappings
Provisioning A Device
IDS Device Mesh ServicesGenerate 1024b RSA key pair
POST /Device (SAML token)
IDS device cert kIDS
Generate self-signed SAML token
Device resource/links/ticket
Register device( public key)
GET /Identities (user IDS ticket)
User resource/links/ticket
PUT /Identities/{ID}/DeviceClaims
Bringing A Device Online
Device Mesh Services
GET /Device (SAML token)
Device resource/links/ticket
POST /Devices/{ID}/NotificationQueues
Queue URL
POST /devices/{ID}/DeviceConnectivityEntry
GET QueueURL
Notifications (if any)
Authorizing A Device For A Folder
Device Mesh Services
GET /Identities (user’s IDS ticket)
Identity resource/links/ticket
GET /Identities/{ID}/DeviceClaims
Devices claimed by this user
POST /MeshObjects/{ID}/Mappings
Scenario Demos
Conceptual demos – not all are supported/available in SDK CTP
creator
creator
consumer
processorconsumer
rich end-point
Content Consumer: Picture Frame
Mental model: Application with delegated read authorization
Mesh Services
Delegated Auth
Content Creator: Camera
Mental model options: File-system integration with local client Application with delegated write authorization
Live Operating Environment (client)Local FS
Live Operating Environment (cloud)
Appliance: NAS
Mental model: Mesh-aware device Mesh Application with delegated read/write
authorization for configuration
Live Operating Environment (cloud/client)
Delegated AuthManagement
application
Device Mapping
Rich Device: Hewlett Packard Photosmart A637
Mental model: Full Mesh Device with delegated authorization
managed by platform experience
Rich Device: Intel® Remote Wake Technology
Mental model: Embedded agent that participates on
behalf of the Mesh Runtime even in S3
Mesh runtime
Intel IRWT agent
Mesh services
Establish connectivity and queues
Configure with queue URL
Listen on behalf of device
Wake up!
PC Goes to Sleep
Device Roadmap
Today (Live Framework CTP) Delegating authorization to apps/services is
easy Creating a new device is not supported
Future: thinking about how to support new device types with the right Programmability UX integration Cross-platform support
Summary
The Mesh is most interesting with a wide range of devices
We will support a full device model in the long term
For now, delegated authorization enables many scenarios
BB05 Live Services: Building Applications with the Live Framework
BB51 Live Services: Programming Live Services Using Non-Microsoft Technologies
BB31 Live Services: FeedSync and Mesh Synchronization Services
BB34 Live Services: Notifications, Awareness, and Communications
Related Sessions
Evals & Recordings
Please fill
out your
evaluation for
this session at:
This session will be available as a recording at:
www.microsoftpdc.com
Please use the microphones provided
Q&A
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.