1 / 25

Live Services: The Future Of the Device Mesh

BB35. Live Services: The Future Of the Device Mesh.  Jeremy Mazner Program Manager Microsoft Corporation. Live Services. Users. Devices. Applications. Synchronization. Mesh Services. Identity. Directory. Storage. Communications and Presence. Search & Geospatial.

alida
Download Presentation

Live Services: The Future Of the Device Mesh

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BB35 Live Services: The Future Of the Device Mesh  Jeremy Mazner Program Manager Microsoft Corporation

  2. Live Services Users Devices Applications Synchronization Mesh Services Identity Directory Storage Communications and Presence Search & Geospatial

  3. Device Scenarios consumer creator rich end-point processor consumer creator

  4. demo Device Platform Experience

  5. Interacting With Mesh Services • 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 App paradigm Device paradigm App paradigm Device paradigm

  6. A Tale Of Two Paradigms

  7. Delegated Authorization (Simplified) I want to use this app This user wants to authorize me Do you really want to authorize this app? Yes indeed! Here’s your token See also BB22 Identity: Live Identity Services Drilldown BB30 Live Services: Building Mesh-Enabled Web Applications…

  8. What Defines A Mesh Device? Queue Service Device Connectivity Service Directory Service Storage Service MeshObject Transient properties Persistent properties Device mappings Notifications MeshObject MeshObject DeviceID

  9. Provisioning A Device IDS Device Mesh Services Generate 1024b RSA key pair Register device( public key) IDS device cert kIDS Generate self-signed SAML token POST /Device (SAML token) Device resource/links/ticket GET /Identities (user IDS ticket) User resource/links/ticket PUT /Identities/{ID}/DeviceClaims

  10. 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)

  11. 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

  12. Scenario Demos consumer creator • Conceptual demos – not all are supported/available in SDK CTP rich end-point processor consumer creator

  13. Content Consumer: Picture Frame • Mental model: • Application with delegated read authorization Delegated Auth Mesh Services

  14. 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)

  15. Appliance: NAS • Mental model: • Mesh-aware device • Mesh Application with delegated read/write authorization for configuration Live Operating Environment (cloud/client) Device Mapping Delegated Auth Management application

  16. Rich Device: Hewlett Packard Photosmart A637 • Mental model: • Full Mesh Device with delegated authorization managed by platform experience

  17. 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 PC Goes to Sleep Listen on behalf of device Wake up!

  18. 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

  19. 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

  20. Related Sessions • 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

  21. Evals & Recordings Please fill out your evaluation for this session at: This session will be available as a recording at: www.microsoftpdc.com

  22. Q&A Please use the microphones provided

  23. © 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.

More Related