Using Web Services for RFID Device Management

1
Using Web Services for RFID Device Management

• Microsoft Corporation

2
Agenda

• Introducing Web Services
• Why Web-Services for DCI
• Introducing DPWS
• Value proposition for Device Vendors
• CAPWAP Preliminary analysis

3
Web Services Primer
Eventing
Metadata
4
Contracts and specs and protocols
class IRFIDService HRESULT Discover(int
deviceId) HRESULT Config()
5
Contracts and specs and protocols
WS-Addressing
HTTP
WS-Discovery
6
Contracts and specs and protocols
POST /37f86d35-e6ac-4241-964f-1d9ae46fb366 HTTP/1.
1 Content-Type application/soapxml ltsoapenvelo
pegt ... ... ltrfiddiscovergt
ltrfiddevIdgt1lt/rfiddevIdgt
ltrfidIPgt192.168.0.3lt/rfidIPgt
lt/rfiddiscovergt lt/soapbodygt lt/soapenvelopegt
7
Why Web Services for DCI ?

• Built on well understood XML
• Type system simple types, derivation, namespaces
• Schema language
• Wire format
• Rich set of layered, expert specifications
• Addressing
• Discovery
• Security
• Eventing
• Reliable messaging
• Transactions

8
Why Web Services contd.,

• Layered architecture, Composable
• Extensible Learning from Windows device partners
• XML protocols are more extensible, better
  debugging experience
• New scenarios for device management
• Multiple subscribers to device events
• Software vendors can easily build solutions
• Use a WSDL in a IDE environment
• Direct management from Enterprise Management
  consoles
• Loose coupling allows platform servers and
  devices to evolve separately

9
Why Web Services contd.,

• Rich tool support for WS
• Code-generation, Debugging, Programming
  environment
• Web Service stacks available
• gSOAP for non Windows
• Windows Communication Foundation
• WSDAPI on Vista
• .Net Micro Framework
• Less code needs to be written by platform servers
  and devices

10
DPWS

• Device Profile for Web Services.
• A WS profile designed with resource constrained
  environments in mind.
• Organizes the most relevant WS- specs
• Windows platform discovery and management support
  for network connected devices
• Available stacks
• WSDAPI for Windows
• DPWS Core on gSOAP
• RFID profile defined on top of DPWS

11
Value Proposition for Device Vendors

• Readily available WS stacks significantly reduce
  development costs
• Partners of device vendors can create device
  management tools easily with WSDLs
• New scenarios open up device to cloud, directly
  managed from enterprise management software
• Rich opportunities for RFID

12
CAPWAP Our analysis

• No separation between protocol and binding
• Reinvents many protocols discovery,
  Fragmentation/Chunking, Reliability
• Security based on DTLS which is not widely
  deployed
• No out-of-the-box stacks available
• Little support for eventing
• Network centric. RFID standard should be
  enterprise centric i.e. friendly to management
  software etc.