Archives
- December 2011
- June 2011
- May 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- December 2009
- October 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- November 2008
- July 2008
- April 2008
- February 2008
- November 2007
- August 2007
- June 2007
- April 2007
- March 2007
- February 2007
- August 2006
- September 2005
- May 2005
- October 2004
- June 2004
Tag Archives: oneapi
Mobile World Congress 2011 Report
Last month’s Mobile World Congress in Barcelona saw a return to buoyancy in the mobile industry, with the GSMA reporting record attendance figures. Delegates were literally bombarded with industry news: Nokia’s alliance with Microsoft, a plethora of LTE trials around the globe, and absolutely unparalleled interest in developer programs from all the major handset and network players.
One such initiative is the GSMA’s OneAPI project, of which Locatrix is a long-standing supporter. The OneAPI (“One” stands for Open Network Enablers) standard provides a baseline reference for HTTP/RESTful APIs to access core network services such as location, messaging and charging, and the GSMA’s AppGarage booth in Hall 7 at the Congress was a busy thoroughfare for interested operators and developers.
Locatrix was delighted to again be asked by the GSMA to support the program by running demonstrations on the booth, and gave hundreds of presentations to delegates of our Developer Portal solution, which provides an immediate application support program for network APIs.
Significantly, we also saw massive interest in our social shopfront solutions, as deployed by Telstra and other operators. These, like all our hosted application services provide operators with a new engagement and promotional channel to their customers for services, content and other offers, producing numerous ARPU and retention benefits.
We’ve been busy since Barcelona fielding interest from operators in Asia and Europe for these solutions, and also preparing for new deployments. Please get in touch if you’d like to learn more about any of our OneAPI or social networking solutions for mobile operators.
Locatrix at Mobile Asia Congress
Locatrix were guests of the GSMA at last week’s Mobile Asia Congress in Hong Kong, providing the OneAPI booth with resources, demonstrations and hands-on assistance to promote the GSMA’s OneAPI initiative to attending mobile operators.
Locatrix Product Analyst Reuben So said that interest in the OneAPI was strong throughout the event, with many operators and developers hearing about it through the WAC announcement, and wanting to hear more.
“We provided demos of our OneAPI-compliant application solutions, as well as our Developer Portal solution right throughout the two-day exhibition,” said So. “There was keen interest from both mobile developers who want to access operator enablers and of course from the operators themselves.”
Locatrix has been an active participant in the GSMA’s OneAPI project since early 2009, and has staged a proof-of-concept portal and OneAPI endpoint service at http://oneapi.locatrix.com throughout 2010.
“Leveraging our solutions is the most cost-effective way a mobile operator can provide OneAPI-compliant developer interfaces,” says Mark White, Locatrix CEO. “We can help mobile operators quickly engage their own developer communities, leveraging the long tail of Web 2.0 innovation in their regions.”
For more information on the Locatrix Developer portal, please visit our solution page or OneAPI pilot site.
Mashups and the OneAPI
If you’ve arrived here after clicking on a link in a Twitter message, welcome! Please read on.
Historically, providing developer-level access to any features of a mobile network has been tricky, to say the least. Even with the relevant service provisioning completed, you’re still stuck with a myriad of interfaces, standards, web protocols and security methods. And that’s just with one operator. As soon as you hit your second there’s usually a whole new set of enabler access methods to implement.


