Mobile Location with AIMS - Consideration for beta testers

We hope that the beta testing is underway in a good and positive way. However, here we would like to point out a limitation of the Mobile Location enabler that directly affects one of the major functionalities of the AIMS project. This will also be true for everyone using the enabler in their projects.

The Mobile Location enabler can only be used after obtaining a valid API key. However, with every key there is a quota limitation to lookup the mobile location. If the quota expires, the location lookup fails that directly influences the application's functionality. If we have the correct information, the quota is 100 lookups per day (please correct if not). However, we have experienced that sometimes the location lookup was not functional with the enabler even with lesser lookup calls.

During the development of the AIMS projects, the 100 lookup quota was never exceeded in a single day. But, we did experience false locations (usually 0.0) on the same place where we already received the correct location earlier. This is a matter of concern for us!

During the beta testing, if such a situation occurs, then the impression of the application is directly affected. Previously we also identified another issue with the same enabler:

http://www.ericssonapplicationawards.com/team/aims/blog/mobile-location-...

With this post, we would like to ask Ericsson representatives, as to how these issues will be addressed during the beta test. If the location lookup fails because of the enabler limitation, how is the application function be graded? This is important for all because in this case it is not the application that malfunctions.

We would appreciate if someone could respond to clarify such doubts and suspicions for all.

The AIMS team