Overview of Windows Vista Devices and Windows Communication Foundation (WCF)
54
-
Upload
jorgen-thelin -
Category
Technology
-
view
675 -
download
2
Transcript of Overview of Windows Vista Devices and Windows Communication Foundation (WCF)
The Windows Communication Foundation
Jorgen ThelinJorgen ThelinConnected Systems DivisionConnected Systems Division
Microsoft CorporationMicrosoft [email protected]@microsoft.com
MOBILE EMPLOYEESMOBILE EMPLOYEES CUSTOMERSCUSTOMERS MOBILE EMPLOYEESMOBILE EMPLOYEESCUSTOMERSCUSTOMERS
The Imperative to ConnectThe Imperative to Connect
“What API should I use?”
“How do I build service-oriented systems?”
“How can I send messages securely & reliably?”
“How do I develop interoperable
applications?”
What We Heard From PeopleWhat We Heard From People
Windows Communication FoundationWindows Communication Foundation
The Unified The Unified Programming Programming
Model For Model For Rapidly Building Rapidly Building
Service-Oriented Service-Oriented ApplicationsApplications
Windows Communication FoundationWindows Communication Foundation
INTEROPERABILITY PRODUCTIVITYSERVICE-ORIENTED
DEVELOPMENT
• Broad Support for WS-* specifications
• Compatible with existing MS distributed application technologies
• Unifies today’s distributed technologies
• Attribute-based development
• Visual Studio 2005 integration
• Enables development of loosely-coupled services
• Config-based communication
PRODUCTIVITYPRODUCTIVITY
InteropInteropwith otherwith otherplatformsplatforms
ASMX
Attribute- Attribute- BasedBased
ProgrammingProgramming
Enterprise Services
WS-*WS-*ProtocolProtocolSupportSupport
WSE
Message-Message-OrientedOriented
ProgrammingProgramming
System.Messaging
ExtensibilityExtensibilityLocation Location
transparencytransparency
.NET Remoting
Unified Programming ModelUnified Programming Model
• WCF extends the .NET Framework
• Services are built in Visual Studio 2005 using any .NET programming language
WCF Composable ArchitectureWCF Composable Architecture
Service Model Layer
Influences and adds to the programming model based on
incoming messages
Messaging Layer
Moves messages backand forth and adds transfer semantics
(channels)
ServiceServiceCodeCode
Transaction Behavior
CLR Type Integration
Instancing Behavior
SecurityChannel
TCP Transport
SecurityChannel
TCP Transport
Transaction Behavior
CLR Type Integration
WCF Composability in ActionWCF Composability in ActionService Model LayerService Model Layer Messaging LayerMessaging Layer
BehaviorsBehaviors ChannelsChannels
Transaction Behavior
CLR Type Integration
Instancing Behavior
SecurityChannel
HTTP Transport
Custom Channel
Reliable Messaging
Queue Transport
MSMQ Integration
TCP Transport
Named Pipes
Throttling Behavior
Error Handling Behavior
Concurrency Behavior
Metadata Behavior
Custom Behavior
HTTP Transport
TCP Transport
SecurityChannel
Custom Channel
Reliable Messaging
CLR Type Integration
Instancing Behavior
Transaction Behavior
Bin
din
gB
ind
ing
AddressAddress
ContractContract
WCF Runtime ArchitectureWCF Runtime Architecture
20,379 lines security
5,988 lines reliable messaging
25,507 lines transactions
Total lines 56,296
4,442 lines infrastructure
class HelloService { [WebMethod] public String Hello(String Greeting) {
X509CertificateCollection collection = new X509CertificateCollection();IntPtr blob = Marshal.AllocHGlobal(Marshal.SizeOf( typeof(CRYPTOAPI_BLOB))); IntPtr data = (IntPtr)((int)blob + Marshal.SizeOf(typeof(CRYPTOAPI_BLOB)));…
SeqAckRange range = new SeqAcknRange(id, low, high );SeqAckRange[] ranges = { range };ReliableQueue.ProcessAcks( ranges );…
hr = pITxDispenser->BeginTransaction (NULL, ISOLATIONLEVEL_SERIALIZABLE, 0, pITxOptions, &pITransaction);…
return Greeting; }}
Using Visual Studio .NET Using Visual Studio .NET 20032003
Productivity - DIYProductivity - DIY
10 lines security
1,804 lines reliable messaging
25,507 lines transactions
Total lines 27,321
class HelloService { [WebMethod] public String Hello(String Greeting) {
foreach ( SecurityToken tok in requestContext.Security.Tokens { X509SecurityToken token = tok as X509SecToken }
… SeqAckRange range = new SeqAcknRange(id,low,high ); SeqAckRange[] ranges = { range }; ReliableQueue.ProcessAcks( ranges ); …
hr = pITxDispenser->BeginTransaction (NULL, ISOLATIONLEVEL_SERIALIZABLE, 0, pITxOptions, &pITransaction); …
return Greeting; }}
Using Visual Studio .NET 2003 and Using Visual Studio .NET 2003 and WSEWSE
Productivity - WSEProductivity - WSE
1 line security
1 line reliable messaging
1 line transactions
Total lines 3
Using Using Visual Studio 2005Visual Studio 2005 and and IndigoIndigo
[ServiceContract(SecureChannel, SecurityMode =“Windows")][Reliability(Guarantees.ExactlyOnce | Guarantees.InOrder)][ServiceContract]class HelloService { [ServiceOperation(TransactionFlowAllowed = true)] String Hello(String Greeting) { return Greeting; }}
Productivity - WCFProductivity - WCF
INTEROPERABILITYINTEROPERABILITY
SIDE-BY-SIDESIDE-BY-SIDE
InteropInterop
UPGRADEUPGRADE
Investment ProtectionInvestment Protection
XMLXML
MessagingMessaging
SecuritySecurity TransactionsTransactionsReliable Reliable MessagingMessaging
Me
tad
ata
Me
tad
ata
WS-* Protocol SupportWS-* Protocol Support
Components of Business InteroperabilityComponents of Business Interoperability
• Agreed syntax representations• E.g. XML
• Agreed protocols• E.g. SOAP + WS-* specs (such as WS-ReliableMessaging)
• Agreed payload formats• E.g. HL7 schemas for healthcare data
• Profiled composition• E.g. Pre-defined options to ensure functionality
• Agreed business scenarios• E.g. Well defined interaction scenarios / use cases
Interop ProfilesInterop Profiles
• Define a subset of specifications that are:• Composable• Scoped• Work together
• Examples:• Secure RM – WS-ReliableMessaging +
WS-Trust/SecureConversation/Security• ACORD Messaging Profile – WS-* + ACORD payload schemas
• Who defines the profile?• Vertical domain org – eg. ACORD• Horizontal org – eg. WS-I• Customer – singly or in groups
Profile Recipe: Staple, Redline, Glue – Device Profile ExampleProfile Recipe: Staple, Redline, Glue – Device Profile Example
• “Staple”• Pull relevant specs into scope
• “Redline”• Add constraints on use of
those specs
• “Glue”• Define missing bits between
specs
• Some will migrate back into specs
SOAP 1.2WS-
AddressingWS-Metadata Exchange
WSDL 1.1WS-
DiscoveryWS-Eventing
ThisModelMetadataThisDevice
Metadata
ActionFilter
ConformanceClaim
PolicyAssertionsPolicy
Assertions
Why Do We Need Interop Profiles?Why Do We Need Interop Profiles?
• Need to constrain (soften) runtime options to achieve out-of-box interoperability• WS-* Architecture is designed for general applicability across a wide
range of industries / scenarios• Often too much optionality in the base specifications
• Tailor to specific domain / environment• E.g. Devices Profile only requires SOAP 1.2 not SOAP 1.1 to lower
implementation footprint
• Guide implementation and deployment choices
• Achieve a proven composition of protocols and payloads
• Allows simplification of application deployment • e.g. WCF allows selection of interop profile to use
SERVICE SERVICE ORIENTATIONORIENTATION
PolymorphismPolymorphismEncapsulationEncapsulationSubclassingSubclassing
Message-basedMessage-basedSchema+Contract+PolicySchema+Contract+PolicyBroad InteropBroad Interop
Location TransparentLocation TransparentTight CouplingTight CouplingRuntime MetadataRuntime Metadata
Object-Oriented Service-OrientedComponent-Oriented
1980s 2000s1990s
From Objects to ServicesFrom Objects to Services
SERVICE ORIENTATIONSERVICE ORIENTATION
Compatibility Based On PolicyCompatibility Based On Policy
Share Schema & Contract, Not Share Schema & Contract, Not ClassClass
Services Are AutonomousServices Are Autonomous
Boundaries Are ExplicitBoundaries Are Explicit
Four Tenets of Service OrientationFour Tenets of Service Orientation
WS DEVICESWS DEVICES
Connected Devices – Ad-hoc / Unmanaged Connected Devices – Ad-hoc / Unmanaged Environment ExampleEnvironment Example
• Joe works for a health care provider. He visits a patient at home and uses his laptop to discover and configure a sensor in the client’s location in ad-hoc mode.
After device discovery, Joe changes the sensitivity level of the sensor and directs the sensor to send notifications to a monitoring server in his office.
Provider’s OfficeCustomer’s Home
Notifications
Configure
Ad-hoc Discovery
Sensor
ProtocolDMRCapabilities
DMRCommands
DMREvents
ProtocolIGDCapabilities
IGDCommands
IGDEvents
Devices ProfileDevices ProfileAssurances
Messaging
SOAP
WS-Security
MTOMWS-Addressing
Metadata
WSDL
WS-MetadataExchange
XML Schema
TLS
Foundation
SOAP / HTTP
MIMEXML Infoset
XML 1.0XML
Namespaces
BP 1.1 Sec. 4
DeviceExtensions
ProtocolPrintCapabilities
PrintCommands
PrintEvents
WS-EventingWS-TransferWS-Policy
SOAP / UDP
WS-Discovery
Vista WS device supportVista WS device support
• Printers• “Plug and Play” experience for network printers• Security
• Control over who can connect to the printer• Privacy of data sent to the printer
• Rich printer status
• Scanners• “Plug and Play” experience for network scanners
• enable one-button scanning
• Secure scan delivery
Vista WS device supportVista WS device support
• PC Discovery
• Messenger - People Near Me
• BITS - Background Intelligent Transfer Service
• Projectors• Integration with current IT systems
• Remote diagnostics and configuration• Asset and usage tracking
• Speeds flow of meeting• Automatic display and audio settings• Easy to transition between presenters
Resources - Web Services On DevicesResources - Web Services On Devices
• Web Services• http://msdn.microsoft.com/webservices/default.aspx• http://msdn.microsoft.com/windowsvista/connected/
• Web Services Feedback Workshops• http://msdn.microsoft.com/webservices/community/workshops/
• Web Services Basics• http://msdn.microsoft.com/webservices/understanding/webservice
basics/default.aspx• Devices Profile for Web Services
• http://msdn.microsoft.com/ws/2006/02/devprof/• WS-Discovery
• http://msdn.microsoft.com/ws/2005/04/ws-discovery/
THE BIGGER PICTURE – WCF and WINFXTHE BIGGER PICTURE – WCF and WINFX
Next Gen Windows Technology FoundationNext Gen Windows Technology Foundation
• Vector-based
• Resolution independent
• Rich media
• 3D user interfaces
Windows Communication FoundationWindows Communication Foundation
• Secure Web servicesSecure Web services• Reliable transacted distributed appsReliable transacted distributed apps• Interoperability with WS-* protocolsInteroperability with WS-* protocols• Any transport and any hostAny transport and any host
• Engine built into platform
• System and human workflow
• Composite apps
Windows Presentation FoundationWindows Presentation Foundation Windows Workflow FoundationWindows Workflow Foundation
Windows InfoCardWindows InfoCard
• Streamlines user registration and one-click loginStreamlines user registration and one-click login• Mitigates common attack vectors (Phishing)Mitigates common attack vectors (Phishing)• Seamless integration with WCFSeamless integration with WCF
Services, Workflow & BizTalkServices, Workflow & BizTalk
WCFWCF WFWFTools and engineTools and engine
for buildingfor buildingworkflow-enable appsworkflow-enable apps
API for buildingAPI for buildingsecure, reliablesecure, reliable
interoperable servicesinteroperable services
Application to application and B2B integrationApplication to application and B2B integration
Connects multiple services built with WCFConnects multiple services built with WCF
Adapters to multiple products like SAP and MQSeriesAdapters to multiple products like SAP and MQSeries
Business activity monitoringBusiness activity monitoring
Vertical solutions and industry acceleratorsVertical solutions and industry accelerators
Message transformation servicesMessage transformation services
Enterprise single sign-onEnterprise single sign-on
End-to-end health and activity trackingEnd-to-end health and activity tracking
And more…And more…
WinFX Ship VehicleWinFX Ship Vehicle
• Down-level support on Windows XP and Windows Server 2003
• Consistent development experience
• Optimizations for Vista
Windows Vista introduces breakthroughs in user experience, security
and reliability, enabling you to build applications that bring clarity to the
user's complex world of information.
WinFX Beta1WinFX Beta1
WinFX Ships!WinFX Ships!
July 2005July 2005
Nov 2006Nov 2006
WinFX Feb CTPWinFX Feb CTP Feb 2006Feb 2006
Getting WinFXGetting WinFX
• Start programming with Visual Studio 2005Start programming with Visual Studio 2005
• Download and evaluate WinFXDownload and evaluate WinFX
• Give us your feedback!Give us your feedback!
Take the Next StepTake the Next Step
Backup SlidesBackup Slides
Services and consumers are Services and consumers are independently versioned, independently versioned, deployed, operated, and secured.deployed, operated, and secured.
Services are Services are autonomousautonomous
Data never includes behavior; Data never includes behavior; Objects with data and behavior are Objects with data and behavior are a local phenomenon.a local phenomenon.
Share schema Share schema & contract, not & contract, not
classclassCapabilities and requirements Capabilities and requirements represented by a unique public represented by a unique public name; Used to establish service name; Used to establish service suitability.suitability.
Compatibility Compatibility based on policybased on policy
Developers opt-in to consuming, Developers opt-in to consuming, exposing, and defining public-exposing, and defining public-facing service façade.facing service façade.
Boundaries Boundaries are Explicitare Explicit
The Four Tenets of Service-OrientationThe Four Tenets of Service-Orientation
Facilitates implementation/platform interop
Independent deployment, versioning, mgmt
Promotes technology reuse
Benefits of Service OrientationBenefits of Service Orientation
ApplicationApplication
Service ModelService Model
MessagingMessaging
Hosting Hosting EnvironmentsEnvironments ASP.NETASP.NETASP.NETASP.NET AvalonAvalonAvalonAvalon WinFormWinFormWinFormWinForm NT ServiceNT ServiceNT ServiceNT Service COM+COM+COM+COM+
TCPTCPChannelChannel
TCPTCPChannelChannel
HTTPHTTPChannelChannel
HTTPHTTPChannelChannel
QueueQueueChannelChannelQueueQueue
ChannelChannel
SecureChannelSecure
ChannelReliableReliableChannelChannelReliableReliableChannelChannel
Instance Instance BehaviorBehaviorInstance Instance BehaviorBehavior
Throttling Throttling BehaviorBehavior
Throttling Throttling BehaviorBehavior
Type Integ. Type Integ. BehaviorBehavior
Type Integ. Type Integ. BehaviorBehavior
TransactionTransactionBehaviorBehavior
TransactionTransactionBehaviorBehavior
ConcurrencyConcurrencyBehaviorBehavior
ConcurrencyConcurrencyBehaviorBehavior
ErrorErrorBehaviorBehavior
ErrorErrorBehaviorBehavior
MetadataMetadataBehaviorBehaviorMetadataMetadataBehaviorBehavior
BinaryBinaryEncoderEncoderBinaryBinary
EncoderEncoder
Text/XMLText/XMLEncoderEncoder
Text/XMLText/XMLEncoderEncoder
…………
……
…………
WASWASWASWAS
WCF Architecture DetailWCF Architecture Detail
• End-to-end Security• Confidentiality, integrity, authentication, authorization• X509, Username/Password, Kerberos, SAML, custom
• End-to-end Reliable messaging• In-order guarantees
• Exactly once guarantees
• Transactions• Guaranteed atomic success or failure across services
WCF Feature OverviewWCF Feature OverviewSecurity, Reliability, TransactionsSecurity, Reliability, Transactions
Windows Activation Service Windows Activation Service (WAS)(WAS)
HTTP.SYHTTP.SYSS
TCP TCP Transport Transport ListenerListener
Named Pipes Named Pipes Transport Transport ListenerListener
HTTP HTTP Listener Listener Adapter Adapter
(IIS7)(IIS7)
NP Listener NP Listener AdapterAdapter
TCP Listener TCP Listener AdapterAdapter
Indigo services can be hosted in any managed Indigo services can be hosted in any managed applicationapplication
ASP.NET, COM+, EXE, NT Service, Windows Forms, AvalonASP.NET, COM+, EXE, NT Service, Windows Forms, Avalon
Windows Activation Service – Used by Indigo and Windows Activation Service – Used by Indigo and IIS7 IIS7
WCF Feature OverviewWCF Feature OverviewHosting ModelsHosting Models
WCF Runtime OverviewWCF Runtime Overview
Process
App Domain
Indigo Runtime
ServiceClass
Endpoint
WS-* Architecture
Assurances
Messaging
SOAP
WS-Security
MTOMWS-Addressing
Metadata
WS-Policy
WSDL
WS-Discovery
UDDI
WS-MetadataExchange
WS-Transfer WS-Enumeration WS-Eventing
XML Schema
WS-ReliableMessaging
WS-Coordination
WS-AtomicTransaction
WS-BusinessActivity
WS-Trust
WS-SecureConversation
Infrastructureand ProfilesWS-ManagementWS-Federation
DevicesProfile
Foundation
SOAP / HTTP
SOAP / UDP
MIME
XML Infoset
XML 1.0XML
Namespaces
WS-* Specifications Process
Step 2Broader
Community Participation
Step 1Initial
Development
Process reconciles conflicting goals• Quality of engineering• Time to market• Breadth of industry support
Step 3Standardization
Step 4Profiling
Increasing Industry ParticipationIncreasing Industry Participation
Specification Specification PublishedPublished
Feedback and Feedback and Interop Interop
WorkshopsWorkshopsRevise specRevise spec Standards OrgStandards Org WS-IWS-I
Idea
WS-* Spec Status
Assurances
Messaging
SOAP
WS-Security
MTOMWS-Addressing
Metadata
WS-Policy
WSDL
WS-Discovery
UDDI
WS-MetadataExchange
WS-Transfer WS-Enumeration WS-Eventing
XML Schema
WS-ReliableMessaging
WS-Coordination
WS-AtomicTransaction
WS-BusinessActivity
WS-Trust
WS-SecureConversation
Infrastructureand ProfilesWS-ManagementWS-Federation
DevicesProfile
Foundation
SOAP / HTTP
SOAP / UDP
MIME
XML Infoset
XML 1.0XML
Namespaces
Step 4 – Approved Standard
Step 3 – Standardization
Step 2 – Workshops & Community Dev
80+ WS-* Workshop Participants 80+ WS-* Workshop Participants Actional Fujitsu Newisys Sharp Labs
AMD Grand Central Nokia Siebel
American Megatrends Hewlett-Packard Oasis Semiconductor Software AG
ANL IBM Oblix Sonic Software
Apache Project iDesign OPC Foundation Sun
Axalto Intel OpenNetwork Systinet
BEA Intermec Oracle Tibco
Blue Titan Iona OSA Technologies Toshiba
Boeing IPO Group Peerless Tyco Safety Systems
Brother Jboss Ping Identity Univ of Sydney
Canon JibxSoap Printronix VeriSign
Choreology KnowNow QuickTree Veritas
CommerceOne Layer 7 Tech Quovadx Visa
Computer Associates Lexmark Reactivity Vitria
Content Guard Lockheed Martin Ricoh WRQ
Cornell University Microsoft Roxio webMethods
Dell Motive RSA Security WSO2
Epson NEC SAP Xerox
Exceptional Innovation NEON Schneider Electric Zoran
Feature Software Netegrity SeeBeyond Unaffiliated
Delivering WS-* - MicrosoftDelivering WS-* - Microsoft
• Microsoft is delivering implementations of all WS-* specs• WSE 2.0 / 3.0
• Interim coverage of evolving security and policy specs
• Indigo• Full coverage of all SRTP Advanced Web Services specs
• Security
• Reliable Messaging
• Transactions
• Policy
• Windows Server 2003 Release 2• WS-Management stack for interoperable system management
• Windows Longhorn• WS-Devices stack for printer and networked device connectivity
VS 2005 + WSE 3.0VS 2005 + WSE 3.0 SOAP 1.1, 1.2 SOAP 1.1, 1.2 WSDL 1.1 WSDL 1.1 MTOMMTOM WS-Addressing 2004/08 (or REC)WS-Addressing 2004/08 (or REC) WS-Security 1.0 WS-Security 1.0
(U/P, X509, Kerberos)(U/P, X509, Kerberos) WS-Secure ConversationWS-Secure Conversation WS-Trust WS-Trust WS-Policy basedWS-Policy based Limited wire Interop with WSE 2.0Limited wire Interop with WSE 2.0
AD Federation Services in R2AD Federation Services in R2 Cross-organizational Identity Cross-organizational Identity
FederationFederation Web SSOWeb SSO
SQL Server 2005SQL Server 2005 SOAP 1.1,1.2 SOAP 1.1,1.2 WSDL1.1WSDL1.1 WS-Security 1.0WS-Security 1.0
ManagementManagement WS-ManagementWS-Management
Microsoft WS-* Product RoadmapMicrosoft WS-* Product Roadmap
VS2003 + Web Services VS2003 + Web Services
Enhancements (WSE) 2.0Enhancements (WSE) 2.0 SOAP 1.1SOAP 1.1 WSDL 1.1WSDL 1.1 WS-Addressing 2004/03WS-Addressing 2004/03 WS-Security 1.0 (U/P, X509, WS-Security 1.0 (U/P, X509,
Kerberos)Kerberos) WS-Secure Conversation WS-Secure Conversation
2004/042004/04 WS-Trust 2004/04WS-Trust 2004/04 WS-Policy basedWS-Policy based
IndigoIndigoWire-level interop with WSE3.0Wire-level interop with WSE3.0
In addition:In addition: MTOMMTOM SAML Token Profile 1.0SAML Token Profile 1.0 Security PolicySecurity Policy WS-Federation Active ClientWS-Federation Active Client
- Enables easy to build STS- Enables easy to build STS WS-RM 2005/02, PolicyWS-RM 2005/02, Policy WS-AT/WS-C 2005/02, PolicyWS-AT/WS-C 2005/02, Policy WS-Policy/PolicyAttachmentWS-Policy/PolicyAttachment WS-MEXWS-MEX
Easy to use Digital Identity / Easy to use Digital Identity / InfoCardInfoCard
Active Directory: FederationActive Directory: Federation
WSD API: Device ProfileWSD API: Device Profile
LonghornLonghornWaveWave
WindowsWindowsServerServer20032003
““R2”R2”WaveWave
MicrosoMicrosoftft
IntelIntel
SunSun
DellDell
AMDAMD AA
CACA AA
SonicSonic AA
gSOAPgSOAP
SystineSystinett
AA
WEBMWEBM
NetIQNetIQ
WS-P
WS-* - Industry AdoptionWS-* - Industry Adoption
Messaging
Security
Assurances
Devices
Mgmt
Metadata
DPWS
WS-
Secure
Conv
WS-S
ecurit
y
WS-T
rust W
S-RM
WS-A
T
MEX
WS-D
Released productReleased product
Public interopPublic interop
AA Co-Author OnlyCo-Author Only
SOAP / W
SDL
MicrosoftMicrosoft
IBMIBM
BEABEA AA
Cape ClearCape Clear
SystinetSystinet
Blue TitanBlue Titan
Rogue Rogue WaveWave
SonicSonic
IONAIONA
JBossJBoss
ChoreologyChoreology
ApacheApache
TibcoTibco
MicrosoftMicrosoft
IBMIBM
BEABEA AA
RSARSA AA
SystinetSystinet
ApacheApache
Layer7Layer7 AA
DataPowerDataPower
CACA AA AA
SUNSUN
SAPSAP
TibcoTibco
IONAIONA
WebMethoWebMethodsds
NokiaNokia
Cape ClearCape Clear
SonicSonic
gSOAPgSOAP
Ping IDPing ID AA
NetegrityNetegrity AA AA
VerisignVerisign AA AA AA
OpenNetwOpenNetworkork
AA AA AA
Oracle/Oracle/OblixOblix
MicrosoftMicrosoft
IBMIBM
BEABEA
SUNSUN
GoogleGoogle
AmazonAmazon
eBayeBay
ApacheApache
WhitemesWhitemesaa
gSOAPgSOAP
RicohRicoh
EpsonEpson
HPHP
XeroxXerox
Fuji-XeroxFuji-Xerox
IntelIntel
CanonCanon
MicrosoftMicrosoft
IntelIntel
CanonCanon
BEABEA AA
WebMethoWebMethodsds
AA
RicohRicoh
EpsonEpson
HPHP
XeroxXerox
Fuji-XeroxFuji-Xerox
BrotherBrother
ToshibaToshiba
ExceptionaExceptional l InnovationInnovation
PeerlessPeerless
SchneiderSchneider
SystinetSystinet
gSOAPgSOAP
LexmarkLexmark AA
MicrosoftMicrosoft
IBMIBM AA
BEABEA AA
SAPSAP AA
SunSun AA
VerisignVerisign AA
SonicSonic
Layer 7Layer 7
ApacheApache
CACA AA
WebMethoWebMethodsds
AA
SystinetSystinet
gSOAPgSOAP
MTOM
© 2003-2006 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view at the time of publication and is subject to change.
WS-M
WS-X
Fer /
Enum
WS-F
ed
Connected Devices – Ad-hoc / Unmanaged Connected Devices – Ad-hoc / Unmanaged Environment ExampleEnvironment Example
• Joe works for a health care provider. He visits a patient at home and uses his laptop to discover and configure a sensor in the client’s location in ad-hoc mode.
After device discovery, Joe changes the sensitivity level of the sensor and directs the sensor to send notifications to a monitoring server in his office.
Provider’s OfficeCustomer’s Home
Notifications
Configure
Ad-hoc Discovery
Sensor
Connected Devices – Managed Environment Connected Devices – Managed Environment ExampleExample
• Joe works for a health care provider. He visits a patient at home and uses his laptop to discover and configure a sensor via discovery proxy. After device discovery, Joe changes the sensitivity level of the sensor and directs the sensor to send notifications to a monitoring server in his office.
Provider’s OfficeCustomer’s Home
Notifications
Configure
SensorDiscover
via DP
HelloDP
