[Fiware-sc-challenge] Fwd: FW: Fi-ware (LocationGE usage at Campus Party)

[Fermín Galán Márquez]

Hi,

FYI, last-minute information of general interest about LOCS GEi for Campus Party.

For any further question or clarification about this GEi, please address it to its owners: alain.lesueur at thalesaleniaspace.com<mailto:alain.lesueur at thalesaleniaspace.com> and remi.challamel at thalesaleniaspace.com<mailto:remi.challamel at thalesaleniaspace.com>

Best regards,

------
Fermín



From: LESUEUR Alain [mailto:alain.lesueur at thalesaleniaspace.com]
Sent: Friday, January 24, 2014 11:52 AM
Subject: RE: Fi-ware (LocationGE usage at Campus Party)


<snip>



The locationGE is not available in FI-LAB, but you will be able to use a global instance in the Fiware TestBed : location2.testbed.fi-ware.eu (access will be opened to campus party IPs).



For you information, this locationGE  instance does not allow you to request real positioning of mobile devices, but will give you some flexibility to simulate  a fleet of mobile terminals and get their positions.



For your information, this Fleet Simulation tool is not directly part of the Location GE core location-based services. You can have a look at the Fiware Wiki at

http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Data.Location for a functional overview of this simulation tool.

Moreover, the Fleet Simulation Tool exposes also A RESTFul API to manage the simulation for a set of terminals (start/pause/stop simulation, create/update/remove route). It is actually used in the Fiware Live Demo to simulate the move of technician trucks.

You can find information on that API in the Fiware Wiki at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/LOCS_-_Unit_Test_Plan., chapter 1.

Don't forget at first step is to register the mobiles and their simulation paths using POST request http:// location2.testbed.fi-ware.eu:8111//testtool/simulation/mobilepaths

To finish, find here below some templates of accepted positioning requests on location GE (refer to Open specifications for full workflows description at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Location_Server_Open_RESTful_API_Specification_(PRELIMINARY))<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Location_Server_Open_RESTful_API_Specification_%28PRELIMINARY%29%29>.

For all these requests, if you receive a TIMEOUT location retrieval status, it means that the server does not succeed to contact the mobile Terminal.
In the mobile fleet simulated environment installed in the global instance, the root cause will be probably either that the simulation tool is not started or the mobile is not registered in the simulation.

Use the GET http:// location2.testbed.fi-ware.eu:8111/testtool/scenario/status to check that a scenario is applied and currently running.
Nota : Trigger scenarios needs LocationGE-TriggerSubscription scenario set-up. If you are using simple location query, selects the LocationGE-LocationQuery scenario (PUT http:// location2.testbed.fi-ware.eu:8111/testtool/scenario/control?select= the LocationGE-LocationQuery)



1)      Single Location Query example on testbeb location2 instance

Send the GET Request :

GET location2.testbed.fi-ware.eu:3128/location/v1/queries/location?requester=locationGE:fiware&address=33611223844&requestedAccuracy=50&acceptableAccuracy=60&maximumAge=100&tolerance=DelayTolerant

Change the MSISDN in your application context.


2)      Location periodic subscription request example

Send the following POST Request
POST location2.testbed.fi-ware.eu:3128/location/v1/subscriptions/periodic

<tl:periodicNotificationSubscription xmlns:common="urn:oma:xml:rest:netapi:common:1" xmlns:tl="urn:oma:xml:rest:netapi:terminallocation:1">
<tl:clientCorrelator>0003</tl:clientCorrelator>
<tl:callbackReference>
   <common:notifyURL>subscription end point url </common:notifyURL>
   <common:callbackData>4444</common:callbackData>
</tl:callbackReference>
<tl:requester>locationGE:fiware</tl:requester>
<tl:address>tel:+33611223844</tl:address<tel:+33611223844%3c/tl:address>>
<tl:requestedAccuracy>10</tl:requestedAccuracy>
<tl:frequency>10</tl:frequency>
<tl:duration>100</tl:duration>
</tl:periodicNotificationSubscription>

Change the MSISDN, the subscription endpoint, frequency and duration (and optionally clientCorrelator and callback data ) in your application context.


3)      Location area event subscription request example

<tl:circleNotificationSubscription xmlns:common="urn:oma:xml:rest:netapi:common:1" xmlns:tl="urn:oma:xml:rest:netapi:terminallocation:1">
<tl:clientCorrelator>0003</tl:clientCorrelator>
<tl:callbackReference>
   <common:notifyURL>subscription end point url </common:notifyURL>
   <common:callbackData>4444</common:callbackData>
</tl:callbackReference>
<tl:requester>locationGE:fiware</tl:requester>
<tl:address>tel:+33611223844</tl:address<tel:+33611223844%3c/tl:address>>
<tl:latitude>100.23</latitude>
<tl:longitude>-200.45</tl :longitude>
<tl:radius>500</tl :radius>
<tl:trackingAccuracy>10</tl:trackingAccuracy>
<tl:enteringLeavingCriteria>Entering</tl:enteringLeavingCriteria>
<tl:checkImmediate>true</tl:checkImmediate>
<tl:frequency>10</tl:frequency>
<tl:duration>100</tl:duration>
<tl:count>5</tl:count>
</tl:circleNotificationSubscription>

Change the MSISDN, the subscription endpoint, frequency and duration, geographic definition of circle area (and optionally clientCorrelator and callback data ) in your application context.

Cordialement / Best Regards.
Alain.

[@@THALES ALENIA SPACE INTERNAL@@]

CCSL/LPLS -- Software Technology Product Line Department  --  Mission Control Center Architect
Tel : +33 (0)5 34 35 68 95  /  Fax : +33 (0)5 34 35 58 45
Porte : H 213  /  E-Mail : Alain.Lesueur at thalesaleniaspace.com<mailto:Alain.Lesueur at thalesaleniaspace.com>

<snip>


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-sc-challenge/attachments/20140124/3964e1f6/attachment.html>