Mobility comes down to the lines between online and offline blurring rapidly, with organizations sprinting to put the infrastructure in place to catch up with the trend.
The blurring of the online and offline is happening all around us in a bi-directional manner -- where the customer expects to interact with the business however and whenever they wish and get the same experience regardless of where they are or what they are doing- and for the business to be able to deliver exactly the same information and services to the customer regardless of how or where they choose to interact.
Is this new? Maybe not, but the O2O (online to offline) concept was truly brought it to life by the Tokyo Metro and their recently launched innovative offering for consumers.
Tokyo Metro carries 6.22 million passengers daily. This past September they announced a new service with two partners: the convenience store operator 7-11 Japan and the Ito-Yokado supermarket chain. Read More »
Tags: 7-11, coupon, Hotspot, Japan, location, metro, network, o2o, offline, online, seven eleven, subway, tokyo, tokyo metro, wi-fi, wifi, wireless
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: Cisco, connect, connected mobile experiences, context-aware, customer experience, guest experience, location, location based services, location-aware, location-based, mobile, mobile browser, mobility, network, technology, wi-fi, wifi, wireless
With 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: Cisco, connect, connected mobile experiences, customer experience, guest access, guest captive portal, guest experience, guest portal, location, location based services, location-aware, location-based, mobility, mobilt, network, technology, wi-fi, wifi, wireless
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 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: API, App, app developer, application, application developer, application development, code, Development, engineer, location, location based services, map, mobility, mobility services, mobility services engine, MS API, mse, network, REST, SOAP/XML, technical, technology, wifi, wireless
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: API, Cisco, cmx, connected mobile experiences, HTTP(S) GET, location, location based services, map, mobility services, mobility services engine, mse, real time location, REST, rtls, web developer, XML