LO (Location Object): Difference between revisions
Content deleted Content added
MikeVislocky (talk | contribs) No edit summary |
MikeVislocky (talk | contribs) Edits proposed by G. Caron |
||
| Line 1: | Line 1: | ||
In an emergency calling environment, the LO is used to refer to the current position of an endpoint that originates an emergency call. The LO is expected to be formatted as a Presence Information Data Format – Location Object (PIDF-LO) as defined by the IETF in RFC 4119, RFC 5139, RFC 5491 and extended by RFC 6848 |
In an emergency calling environment, the LO is used to refer to the current position of an endpoint that originates an emergency call. The LO is expected to be formatted as a Presence Information Data Format – Location Object (PIDF-LO) as defined by the IETF in RFC 4119, updated by RFC 5139, RFC 5491, RFC 7459, and extended by RFC 6848 . <br /> |
||
The LO may be: |
The LO may be: |
||
* Geodetic – shape, latitude(s), longitude(s), elevation, uncertainty, confidence and the datum which identifies the coordinate system used. NENA prescribes that geodetic location information will be formatted using the World Geodetic System 1984 (WGS 84) datum; |
* Geodetic – shape, latitude(s), longitude(s), elevation, uncertainty, confidence and the datum which identifies the coordinate system used. NENA prescribes that geodetic location information will be formatted using the World Geodetic System 1984 (WGS 84) datum; |
||