Hi Denis,

> > As requested, this is our initial proposal for a minimal API
> > in order to support E911, based on the 27.007 defined AT
> > commands.
> > 
> > We've discussed internally different names for this API:
> > AGNSSManager or AssistedGlobalNavigationSatelliteSystem,
> > but ended up with the simpler LocationServicesManager.
> > 
> > Looking forward to your comments on this API.
> > 
> > Regards,
> > Simon Lethbridge and
> > Sjur Brændeland
> > ---
> >  doc/location-services-api.txt |   56 +++++++++++++++++++++++++++++++++++++++++
> >  1 files changed, 56 insertions(+), 0 deletions(-)
> >  create mode 100644 doc/location-services-api.txt
> > 
> > diff --git a/doc/location-services-api.txt b/doc/location-services-api.txt
> > new file mode 100644
> > index 0000000..18ef230
> > --- /dev/null
> > +++ b/doc/location-services-api.txt
> > @@ -0,0 +1,56 @@
> > +LocationServicesManager hierarchy
> > +=================================
> > +
> > +Service	org.ofono
> > +Interface	org.ofono.LocationServicesManager
> 
> I actually think LocationServices is enough..

sounds good to me.

> So let me summarize 27.007 briefly.  It defines the following elements
> for +CPOS/+CPOSR:
> 
> - location
> - assist_data
> - pos_meas
> - GPS_meas
> - GPS_assist_req
> - msg
> - pos_err
> 
> So from my understanding +CPOS command can be used to send <location>,
> <GPS_assist_req> and <pos_err> elements.
> 
> And +CPOSR can transfer the following elements from the network:
> <assist_data>, <pos_meas>, <msg>.
> 
> Am I right so far?
> 
> Where does the <GPS_meas> element fall into?
> 
> > +Object path	[variable prefix]/{modem0,modem1,...}
> > +
> > +Methods	dict GetProperties()
> > +
> > +			Returns properties for the modem object. See
> > +			the properties section for available properties.
> > +
> > +			Possible Errors: [service].Error.InvalidArguments
> > +
> > +		void SetProperty(string name, variant value)
> > +
> > +			Changes the value of the specified property. Only
> > +			properties that are listed as read-write are
> > +			changeable. On success a PropertyChanged signal
> > +			will be emitted.
> > +
> > +			Possible Errors: [service].Error.InvalidArguments
> > +					 [service].Error.DoesNotExist
> 
> I think we can get rid of the above two methods, see below...
> 
> > +
> > +		void SendPositioningControl(string xml_element)
> > +
> > +			Send an XML element conforming to the XML DTD for <pos>
> > +			as defined in 3GPP 27.007 Table 8.55-2.  This xml is
> > +			used for transferring data associated with positioning
> > +			requests received via control plane from the network.
> > +			This includes assistance data requests and the results
> > +			of positioning procedures. This method maps directly to
> > +			the 3GPP 27.007 AT+CPOS command.
> > +
> > +
> > +Signals	PropertyChanged(string name, variant value)
> > +
> > +			This signal indicates a changed value of the given
> > +			property.
> > +
> > +		PositioningRequest(string xml_element)
> > +
> > +			Receive an XML element conforming to the XML DTD for
> > +			<pos> in 3GPP 27.007. This xml is used for transferring
> > +			data associated with positioning requests received, via
> > +			control plane, from the network. This includes
> > +			measurement requests and assistance data. This signal
> > +			maps directly to the 3GPP defined +CPOSR unsolicited
> > +			result code.
> 
> How about transforming this signal into an Agent based API instead.  So
> let us have a LocationServicesAgent API with the following rough API:
> 
> LocationServicesAgent
> 
> * Release() - Self explanatory
> * HandleRequest(string xml) - Essentially gets passed the data from the
> +CPOSR unsolicited response.
> 
> We can then add two more methods to the LocationServices interface:
> 
> * RegisterAgent()
> * UnregisterAgent()

Sounds simple and straight forward to me. That way we can even tell the
modem clearly if we have an application handling this or not. And in
addition we can track the lifetime of such an application.

> > +
> > +Properties	boolean NetworkInitiatedProceduresEnabled [readwrite]
> > +
> > +			If NetworkInitiatedProceduresEnabled is False, then
> > +			no Position Requests from the network are accepted.
> > +			The modem is not enabled for positioning requests
> > +			from the networks view point.
> 
> This property can then be potentially made redundant.  E.g. if there's
> no agent registered, the network position requests are turned off.  Once
> the agent is registered, they are turned on.
> 
> The SendPositioningControl function can then be tweaked to return an
> error if the Agent is not registered.  I assume there's nothing useful
> we can do without someone handling the data returned by +CPOSR.

Since we are tracking the lifetime of an agent, we could just go one
step further and enforce that only the application that registered the
agent can call this method.

So far this looks like a nice and simple proposal. And it is driven by
an existing standard. I like that.

Sjur, are you guys up to the task of sending an initial atom
implementation and atmodem driver for it?

Regards

Marcel