Cisco Blogs


Cisco Blog > Mobility

Top Coders Win Cisco CMX Mobility Challenge

Over 30 registrants competed in an online global Cisco developer challenge to use the CMX Mobility Services API and CMX in a new app using a simulated environment for a meeting host to automatically launch a WebEx conference, based on the location of the conference room where the meeting is scheduled.  Guidance was provided in a previous blog post, which you too can use to develop innovative applications to create your own Connected Mobile Experience.

topcoder

Numerous impressive submissions demonstrated how straightforward it was to create a new mobile application using the CMX APIs and SDK.  The winning entries submitted code, a video demo, and a read me file, which together conveyed their work using real-time location updates to trigger a context-aware push notification.

First place entry from a brand new TopCoder member “gitsIndonesia” received a check for $1500. It included very clean Android Java code which was well-designed and easy to follow, while applying object-oriented practices. It provided a great example of how to build a new location app from the ground up using the CMX APIs with no changes required for the server simulator since the client (the app) was used for location polling. Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Apple iOS 8 and MAC Randomization: What It means for Cisco’s Connected Mobile Experiences (CMX) Solution

As you may have read, Apple’s iOS 8 will come with some changes to the way MAC addresses are exposed in Wi-Fi probe requests. Apple’s intent was to provide an additional layer of privacy for consumers and target those companies that offer analytics without providing any value to the end consumer. We’ve been getting some questions about what this means and how it impacts our Connected Mobile Experiences (CMX)  solution, so we wanted to clear this up for our customers.

What does this mean for you? 

First and foremost, Cisco has always been dedicated to privacy for our customers and their end-users. There are four aspects of privacy that are built into our CMX solution:

1. Anonymous Aggregate Information: All analytics are based on aggregate, anonymized location data.

2. Permission-based: Users have to opt-in to join a Wi-Fi network or download an app

3. MAC Address Hash: Users’ MAC addresses can be hashed before exposing to 3rd party apps

4. Opt Out: End-users are always presented with the option to opt out of location-based services

The true value of CMX analytics for organizations is in aggregate location data to be used for business analysis to improve the customer experience for end-users. Providing customers with high performing Wi-Fi not only keeps always-on mobile users happy and opens the doors to delighting customers with more personalized experiences, but also helps provide more granularity to those aggregate trends to feed back into the experience creation machine. Win-win.

What does this mean for our CMX value proposition? Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Indoor WiFi Location and Beacons: Better Together

wifibeaconIn just two years, indoor location technology has taken off and attracted a lot of buzz across industries, from retailers to healthcare. But it’s no longer a conversation about just Wi-Fi – the introduction of beacon devices, including iBeacon, has added a new dimension to location technology for IT and their line of business counterparts to grapple with on how to leverage it to better reach their customer base.

Some customers have been asking about beacon technology and how it fits in with Wi-Fi, so let’s start from the beginning:

How do beacons work?

Beacons are sensors that send out Bluetooth low energy (BLE) tracking tags.  These sensors can be placed around a venue, such as a store, and a mobile device can pick up the BLE signal and determine that it is in close proximity. When a mobile app is built off of this technology, it can be used in interesting ways to interact with the end user, such as notifying a customer of a promotion for an item they are close to.

I’m having trouble differentiating Wi-Fi and beacons. What do I need to know? Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Deep Dive: Mobility Services APIs (with Sample Code!)

Last week, my colleague Rajiv walked you through an overview of how our Mobility Services API now supports REST based APIs. As a developer for the Mobility Services Engine (MSE) team, I am very excited about this update because it means that it will be easier for developers to create apps using the MS-API, which hopefully means that more and more organizations will be able to take advantage of the location-based services and functionalities of the MSE. I’m going use this blog to walk you through some of the more technical aspects of the change.

The Basics

The REST API is now widely used in the field of API based web applications. The REST stands for REpresentational State Transfer. It is an architecture that is based on set of six rules, and APIs that support REST follow all those rules, making them RESTful.

Compared to SOAP, REST has better performance, scalability, simplicity, modifiability, visibility, portability, and reliability. For secured REST API transactions, HTTPS is recommended.

RESTful Mobility Services API

7.5 applications, including features from the Connected Mobile Experiences (CMX) solution such as Browser Engage and CMX Analytics, are now supporting REST APIs in addition to the existing SOAP APIs previous releases (backward compatibility).

CMX utilizes the basic authentication scheme to authenticate each REST API request. It utilizes the Authorization header in the HTTP packet. The Authorization header is composed as follows:

- Username and password are combined into a string “username:password”.
- The resulting string literal is then encoded using Base64.
- The authorization method, a space and the string “Basic” is then put before the encoded string.

The API credentials can be accessed from Prime Infrastructure (PI), which manages CMX (page is located under Mobility Services > Specific MSE > System > Users).

As Rajiv mentioned last week, the Mobility Services REST APIs can be grouped in the following way:

-          MAP APIs

-          Real time location APIs

-          Location history APIs

-          Notification APIs

Let’s break them down with use cases to get a better picture of when you’d use which. Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

Cisco Mobility Services APIs go RESTful

As a product manager, I am happy and excited to tell you that Cisco Mobility Services Engine (MSE) now supports REST based APIs. Why am I happy and excited you ask? MSE’s REST based APIs allow web app developers to rapidly develop location aware apps with ease.  Let me walk you through this new feature at a high level, and my colleague will take you through a closer look feature blog next week.

Mobility Services Engine and API support

For readers who are not familiar with the Cisco Mobility Service Engine and the APIs, here’s the gist:

-          Cisco Mobility Services Engine (MSE) works in conjunction with Cisco Wireless LAN Controller (WLC) and Cisco Aironet Access Points (APs) and computes real time location for all Wi-Fi end-points using RSSI based triangulation algorithms.

-          MSE stores real time and historical location of Wi-Fi clients in its database making it a gold mine of data for indoor location. (Remember that GPS technology is not effective for indoor location)

-          This rich store of indoor location data is now available to app developers to query through a REST based API over a secure HTTPS connection.

What can I do with MSE REST APIs?

MSE REST APIs allow web developers to query MSE location database using the HTTP(S) GET method. HTTP response payload can be received in XML or JSON format. Here is a list of resources that are accessible over the REST API. Read More »

Tags: , , , , , , , , , , , , , , ,