Re: [devices-discuss] Web Services For Devices...

[James Blaisdell <james@mocana.com>]

Hello Joe,

A few things immediately pop to mind.  Message size which is inter-related 
to memory and bandwidth limitations is one concern.  This is further 
compounded by XML which is very heavy, compared to packet-based 
communication protocols.  There is a need to allow devices and servers to 
cooperate and negotiate the maximum message size, as well as the content of 
the messages.  Instead of one-message-fits-all, maybe a headless system is 
not interested in full blown synopsis but perhaps just the headline for 
logging purposes.

Security is paramount; which today is a composite of technologies; 
eavesdropping protection, authentication, access, accounting, and 
auditing.  Security and provisioning should go hand-in-hand, since the 
devices may well be connecting directly into corporate network.

Long term, device-to-device communications will be very exciting, but my 
feeling is that manufacturers will get a lot more bang from the market for 
device-to-the-server-in-the-sky.  RF-ID tag on pallet interacting with a 
forklift or shelf is certainly valuable, but that data is worth much more 
being feed into the back office in real-time.

Are people on this list dealing with device security?  Are memory and 
bandwidth a concern?  There are a number of devices connecting to back end 
systems today.  Are there some people on this list that have experience in 
this area they would like to share?  Any recommended software packages for 
doing XML / web services messaging?  Is device-to-device or 
device-to-server more important to people on this list?  What gets people 
excited about web services for devices?

The possibility of devices feeding and digesting meaningful real world data 
across the network --- leveraging today's enterprise web services is 
exciting to me.  Sprinkler systems that can check a weather report, before 
turning on would prevent waste.  Devices that can subscribe to the same 
financial services as my PC allow consumers to chose one data provider, one 
fee.  Devices that can subscribe across the network to firmware image 
updates.  Automated warranty cards and customer care.  None of this is pie 
in the sky, it's happening now, maybe in proprietary, inflexible way, but 
it is happening.

Regards,
James

At 03:08 PM 10/3/2003 -0400, Chiusano Joseph wrote:
>James,
>
>This sounds great. Perhaps we can start by discussing the special needs
>for devices and Web Services vs. (for example) servers and Web Services.
>That is, what are the differentiators? I'm thinking along the lines of
>limited memory, bandwidth issues, security in wireless environments,
>etc. What are your thoughts?
>
>Kind Regards,
>Joe Chiusano
>Booz | Allen | Hamilton
>
>James Blaisdell wrote:
> >
> > This working group needs to leverage existing work that is being
> > conducted within OASIS and other standards initiatives, bringing them
> > all together and applying them to devices. There are positive
> > movements around event driven communications in heterogeneous
> > environments, web services orchestration, composite applications and
> > security that can all be built upon. We need to refine and understand
> > the implications of these "enterprise" services application to the
> > emerging (often resource limited) device network. Over time devices
> > will become more powerful, but we need to forge a path between the
> > here and now, and distant future.
> >
> > The use of networked devices is growing at a lightning pace, driven by
> > the need for OEM's, service providers and customers to add
> > functionality, differentiate products and take cost out of post sales
> > customer support functions. There is also an emergence of several
> > classes of devices that can all benefit from the output of this
> > working group. This market can be portrayed by the following matrix;
> >
> > [599ffd8.gif]
> >
> > - Display centric devices: These are devices that rely on a display
> > Eg. PDA's, HDTV
> > - Headless Devices: These are devices without a display. Eg. Switches
> > and routers
> > - Fixed Position Devices: These are devices that do Eg. MRI machine
> > - Mobile Devices: These are devices that change location Eg. Delivery
> > truck, pallets, mobile phones
> >
> > The problem today is that the majority of the software for devices is
> > proprietary. This results in tightly integrated systems that do not
> > interoperate. To applications developers, the result is a
> > heterogeneous and fragmented market. It has also forced the use of sub
> > optimal components like embedded web servers which do not work well
> > for device centric use scenarios (eg. provisioning, ordering etc.)
> > that will drive real economic value for OEMs, service providers and
> > customers.
> >
> > Through this working group it is possible to define a set of standards
> > that can be applied across all device classes that will allow for
> > services to be exposed in a standard way and for 'any to any' and
> > secure communications to take place in a loosely coupled world. This
> > will benefit all industry participants, OEM's, networking companies,
> > service providers and embedded systems software companies. OEM's will
> > be able to add value added services, with built in greater customer
> > care for end users. Networking companies hardware will act as natural
> > device hubs. Service providers will be able to leverage 3rd party
> > services, and add new service offerings. Embedded systems software
> > vendors will be able to create out of the box solutions that offer
> > total customizability and manageability. And finally, end-customers
> > will greatly benefit from more flexible and customizable solutions.
> >
> > Let me know what you think and what other standards initiatives we
> > should be leveraging here.
> >
> > James Blaisdell
> > CTO, Mocana Corporation
> > Chair - OASIS Web Services for Devices Discussion List