Voicebased generic UPnP Control Point

1
Device and service templates for the Devices
Profile for Web Services
Andreas Bobek, Elmar Zeeb, Hendrik Bohn, Frank
Golatowski, Dirk Timmermann University of
Rostock Faculty of Computer Science and
Electrical Engineering 6th International IEEE
Conference on Industrial Informatics INDIN08 13th
16th July, 2008, Daejeon, Korea
2
Outline

• Problem description
• Device and service frameworks
• UPnP vs. DPWS
• Motivation, requirements, main idea
• Suggested solution
• Impact
• Conclusions

3
Networked devices and services (background)

• special field of application
• research topic for several years
• evolved from the need of interoperable
  cross-platform, domain-spanning devices/services
• some frameworks are already available, none of
  them is widely used
• main requirements
• independent of platform, programming language,
  domain
• plug and play
• eventing
• IPv4/IPv6
• tools

4
Device service frameworks
5
UPnP DPWS stacks

• specified in 1999 prior to Web services (starts
  in 2000)
• same target as DPWS
• pros
• UPnP specification process
• standardized Device Control Protocols (DCP)
• cons
• bad designed/proprietary protocols (SSDP, GENA,
  RPC-based SOAP)
• no security

6
UPnP DPWS stacks

• Web services framework is the SOA technology
  today
• pros open standards, widely deployed, industry
  driven, no fee, software tools
• cons plethora of specifications (protocols,
  bindings, profiles), redundancy, not consolidated
  yet
• DPWS
• special profile for Web services
• targeted for embedded devices (but may be applied
  to usual Web services as well)

7
UPnP DPWS stacks
8
UPnP DPWS stacks
9
Device and service templates

• motivations
• still missed in DPWS
• code generation
• improving discovery
• requirements
• readability
• accessibility
• code generation
• versioning

• main idea
• formal XML documents
• device and service type separation
• types are XML qualified names (QNames)

10
Service template content
11
Service template example
12
Device template content
13
Device template example
14
WS-Discovery revised
15
WS-Discovery revised
16
Code generation
17
Conclusions

• XML-based formal description
• supports code generation
• reuse of DPWS terminology (Hosted, Host,
  Relationship)
• URL templates for fast discovery
• own XML serialization for QNames (allows for
  easier transformation)
• supports versioning (multiple inheritance)