1 / 7

Event Package for Device Information

Event Package for Device Information. Mahfuzur Rahman ( mahfuz@research.panasonic.com ) Brijesh Kumar ( kumarb@research.panasonic.com ) Bin Hu ( bhu@motorola.com ) Ashir Ahmed ( a.ahmed@ntt.com ). Draft Overview. Event Package to retrieve device profile and status information

masato
Download Presentation

Event Package for Device Information

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. Event Package for Device Information Mahfuzur Rahman (mahfuz@research.panasonic.com) Brijesh Kumar (kumarb@research.panasonic.com) Bin Hu (bhu@motorola.com) Ashir Ahmed (a.ahmed@ntt.com)

  2. Draft Overview • Event Package to retrieve device profile and status information • Package name: device-info • The Mime type in Accept header will differentiate between profile and status information • Accept: application/device-profile+xml • Accept: application/MyCamera+xml

  3. Purpose • Why we need this • Device Monitoring • Get Change in Operating Status

  4. Device Profiles • Device Profile only defines common format for core hardware related information which includes Mime type for status information • Currently we do not define a common format for status information but it can be defined later • This event package will use vendor specific Mime type for status information for different classes of devices. • These Mime types will be registered with the IANA by the vendors

  5. Core Profile Data Device Profile (only core information) • Limited set of static attributes • Device type • Name • Model • URL • Software Version • Mime type format for status information • Etc. • Device Status • Operating state • Location • Availability etc.

  6. Feedback from Mailing List • Cullen Jennings - made suggestions to include • add an optional UUID to the profile • add software version. • To make the schema URL and name attributes of a schema object so that the device can lists multiple schema that it can support. • Paul Kyzivat - suggested • Device and AOR relationship clarification • Add clarification to avoid ambiguity between device and service • Also, additional clarification with regards to forking of Subscribe

  7. Next Step • Action!!!!! • Accept as a Working Group Document

More Related