Cisco Blogs


Cisco Blog > Mobility

Create Mobile Web Campaigns with CMX Browser Engage

In the last MSE blog, Reddy Babu talked about the new Location Aware Guest Captive Portal powered by the Mobility Services Engine (MSE). The MSE was first introduced to provide location based information as a core service to the network, but has since built out a suite of location-based services that take the location-based data from the wireless network to the next level. These services are collectively known as the Cisco Connected Mobile Experiences (CMX) solution. As you read in Dr. Brendan O’Brien’s blog last week, we have been introducing more and more features to the CMX solution.

Today I will expand on one of these new features offered by the Connected Mobile Experiences solution: Browser Engage -- which is our new network based location and context aware orchestration platform.

Browser Engage allows organizations to customize the web browsing experience for mobile users in their venue by offering various context-aware value added services. These services, such as indoor navigation and search, are available to the mobile user throughout their mobile web browsing experience. Browser Engage also helps organizations setup their content and serve them to the users based on device location. For example, an organization can deliver coupons or deals to mobile users based on their location within the venue—making the offerings much more relevant to the mobile end user.  Imagine yourself in a mall and a deal shows up on your phone right around lunchtime that is valid at a food court right around the corner.

So, how does it work? Read More »

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

CMX Connect – An Innovative, Location Aware Guest Captive Portal

connect1With the explosion of smart mobile devices, consumers expect to have Wi-Fi access at pubic venues everywhere they go. Venue owners are under pressure to provide reliable Wi-Fi guest access in a simple and easy way. Wouldn’t it be great to be able to do that AND extract some value out of your investment in setting up the Wi-Fi network as well? Cisco Connected Mobile Experience (CMX) is an industry leading solution provides just that: an easy, customizable and location-aware way to onboard guests using CMX Connect, an ability to gain insights into guest behaviors using CMX Location Analytics and an opportunity to engage guests in meaningful ways using CMX Browser Engage.

With MSE Release 7.6 coming out later this year, we wanted to give you a closer look at new feature CMX Connect.  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: , , , , , , , , , , , , , , ,

Deep Dive: Major User Interface Transformation in CMX 7.6

You read about the three flavors of analytics we offer with the Connected Mobile Experiences solution last week. One of the key innovations Evyatar discussed is the a completely transformed user interface for onsite analytics, so I want to give you all a closer look at exactly what enhancements are in store for location analytics CMX 7.6 (available later this year).

Redesigned from the bottom up, the UI update came from a strong team effort to  deliver a solution that is not only relevant to our customers, but intuitive and easy to use for business users. Our vision is that anyone from sales to marketing,  from store management to customer operations should be able to use the tool without having the call the IT guy.

The redesign process considered around the needs and learnings of our early customers, with over 20 individual customer interviews and previews, and incorporated input from proven UI and HCI experts.

The most important feedback was from our customers, and we listened! The new UI contains both overt and subtle changes, all tailored from our customers’ perspective in order to deliver tools they need to make better business decisions, enhance their customers experiences, improve their operational efficiency and increase their revenues

Some of the major UI innovations coming in this release include:

Analytics Dashboard

A new dashboard introduced to deliver key information at a glance when the user first logs in. The dashboard layout can be configured to display the most relevant information to the user so that they can immediately make use of it within the business.

ui1 Read More »

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