All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marko.Ovaska@nokia.com
To: ofono@ofono.org
Subject: RE: [PATCH] doc: Add Location Services API
Date: Fri, 26 Nov 2010 16:29:47 +0100	[thread overview]
Message-ID: <B737AE8337D70F47B693AC85FA440B08328D7512B8@NOK-EUMSG-02.mgdnok.nokia.com> (raw)
In-Reply-To: <129600E5E5FB004392DDC3FB599660D70104DAF2A3@irsmsx504.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]



: Behalf Of Marko.Ovaska(a)nokia.com
: >Sent: Monday, November 22, 2010 10:01 AM
--
: > I'm proposing that either we have
: > a) fully opaque 'raw' 3GPP defined frames between modem and Linux
: > b) or well defined D-BUS API for LCS commands, but keeping the
: assistance payload in 'raw' format


Checked the 27.007 and Sjur's proposal: XML format after, for example +CPOS command, is above a) option with XML formatted payload.

I'll rephrase the ASN.1 formatted opaque option as a2). 

Rationale is that position engine in Linux user space or GPS chip must do ASN.1 processing in handset: Positioning engine uses both OMA specified SUPL server and LCS server in cellular network. Adding new format to cellular network LCS server messages increases work into modem and positioning engine.

Then the ASN.1 formatted interface
void SendPositioningControl(string xml_element)
becomes

void SendPositioningControl(string asn1_element)

and text refers to RRLP format in TS 44.031 and RRC in TS 25.331.




: For the option b, I would tend to not support you. I just recheck the
: 23.032 (Universal GeoGraphical Area Description), and the number of
: ways to express a position with velocity and uncertainty may not make
: the API simple.
: Just have a look for instance the +CMOLR's XML DTD location_parameters.
: :)

Payload gets complicated, I agree. Following the generic oFono interface definitions...

   Marko



  parent reply	other threads:[~2010-11-26 15:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 19:44 [PATCH] doc: Add Location Services API Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2010-11-11 21:49 ` Denis Kenzior
2010-11-11 23:03   ` Marcel Holtmann
2010-11-17  6:34     ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2010-11-15 11:19   ` Simon LETHBRIDGE
2010-11-18  9:50   ` [PATCH] doc: Add Location Services API (resending now that I am on ofono mailing list) Simon LETHBRIDGE
2010-11-22 21:50     ` Joly, Frederic
2010-11-18 10:57   ` [PATCH] doc: Add Location Services API Simon LETHBRIDGE
2010-11-20  1:01 ` Bastian, Waldo
2010-11-20  2:04   ` Bastian, Waldo
2010-11-22  9:01     ` Marko.Ovaska
2010-11-22 23:16       ` Joly, Frederic
2010-11-23 17:16         ` Simon LETHBRIDGE
2010-11-26 15:29         ` Marko.Ovaska [this message]
2010-11-26 16:20         ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2010-11-22 14:04     ` Simon LETHBRIDGE
2010-11-26 16:11   ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2010-12-01 13:35     ` Simon LETHBRIDGE
2010-11-22 15:11 ` [RFCv2] doc: Assisted Satellite Navigation API and Agent API Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2010-11-23 13:28   ` andrzej zaborowski
2010-11-23 15:07     ` Simon LETHBRIDGE
2010-11-23 17:15       ` andrzej zaborowski
2010-11-23 17:24         ` Simon LETHBRIDGE
2010-11-30 13:23   ` Denis Kenzior
2011-01-26 14:52     ` Simon LETHBRIDGE

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B737AE8337D70F47B693AC85FA440B08328D7512B8@NOK-EUMSG-02.mgdnok.nokia.com \
    --to=marko.ovaska@nokia.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.