1 / 9

Vishal K. Singh Henning Schulzrinne Hannes Tschofenig IETF 67, San Diego

Dynamic Feature Extensions to the Presence Information Data Format Location Object (PIDF-LO) draft-singh-geopriv-pidf-lo-dynamic-00.txt. Vishal K. Singh Henning Schulzrinne Hannes Tschofenig IETF 67, San Diego. Requirements and Use Cases. Mechanism to indicate temporal features of entities

senwe
Télécharger la présentation

Vishal K. Singh Henning Schulzrinne Hannes Tschofenig IETF 67, San Diego

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. Dynamic Feature Extensions to the Presence Information Data Format Location Object (PIDF-LO)draft-singh-geopriv-pidf-lo-dynamic-00.txt Vishal K. Singh Henning Schulzrinne Hannes Tschofenig IETF 67, San Diego

  2. Requirements and Use Cases • Mechanism to indicate temporal features of entities • Mechanism to track location of moving objects • Use cases: • Location tracking, Fleet management, Monitoring, Safety of personal • Extends RFC 4119, to carry temporal feature elements

  3. Dynamic Feature Elements Based on GML’s dynamicFeature.xsd • Speed • Measure of the rate of motion • Bearing • Direction e.g., A compass point is specified by a simple enumeration string type (e.g., "N", "NNE") • type gml:DirectionPropertyType • Acceleration • The rate (usually rapid) at which something happens • Elevation • The height of an entity above a reference level; altitude

  4. Example <presence xmlns="urn:ietf:params:xml:ns:pidf“ xmlns:gp=“urn:ietf:params:xml:ns:pidf:geopriv10” xmlns:temp="urn:ietf:params:xml:ns:temporal1“ entity="pres:geotarget@example.com"> <tuple id="sg89ae"> <status> <gp:geopriv> <gp:location-info> <gml:location> ………… </gml:location> <temp:speed uom="#kph">12</temp:speed> <temp:bearing> <temp:CompassPoint>SE</temp:CompassPoint> </temp:bearing> </gp:location-info> <gp:usage-rules> ………… ………… ………… </gp:usage-rules> </gp:geopriv> </status> <timestamp>2003-06-22T20:57:29Z</timestamp> </tuple> </presence>

  5. Protocol Behavior • Indicating the use of dynamic feature PIDF-LO • Indicating units of measure • GML units to measure parameters

  6. Multiple Moving Object Elements • Watchers may request to receive multiple location vector objects together • Use of <timed-presence> to transfer multiple location vector objects <tuple> <status> <gp:geopriv> .......... </gp:geopriv> </status> <timestamp>.....</timestamp> <timed-status from="some time" until="some time"> <gp:geopriv> ............ </gp:geopriv> <gp:geopriv> ........... </gp:geopriv> </timed-status> </tuple> <tuple> ....... </tuple>

  7. Alternatives Considered • Use of ‘MovingObjectStatus’ or its parent element ‘track’ from GML’s dynamicFeature.xsd • To prevent backward compatibility problem we don’t use MovingObjectStatus element • Else <location> element appears twice, once inside <MovingObjectStatus> and another as its sibling.

  8. Open Issues • How to indicate use of dynamic feature PIDF-LO • Proposal • Supporting namespace • Accept: application/pidf+xml; supported="urn:ietf:params:xml:ns:temporal1" • Alternative, registering a token • Accept: application/pidf+xml; supported="geopriv-temporal-features"

  9. Next Steps • Adopt this as WG draft • Submit a new version • Close the open issues • IANA considerations • Revise the text

More Related