Cisco Live Milan 2014 kicked off this morning with an opening keynote by Rob Lloyd. During the session Rob shared Cisco’s vision of the Internet of Everything, and explored the industry trends and technologies that are making that vision a reality. One of these areas is enabled by Cisco’s CMX solutions and our growing ecosystem of partners.
To illustrate how this vision is becoming a reality, a CMX demo was shown on stage. The demo related to a wine producer ( we are in Italy by the way..) who was able to engage with their customers via their mobile app. Enabling the customer find the particular wines they are interested in, interact with the wine maker, get location specific promotions and really deliver a highly personalized and location specific service.
CMX at Cisco Live Day 1:
The whole venue has been designed and setup for WiFi location based services and CMX is running across the complete conference. Read More »
Tags: analytics, App, application, Cisco, cisco live, cmx, Conference, customer, customized, device, Enterprise, experience, heat map, innovation, innovative, interaction, internet, Internet of Everything, keynote, lbs, location, location based services, location specific, location-based, map, mobile, mobility, network, personalized, promotion, rob lloyd, service, technology, venue, wi-fi, wifi, wireless, wlan, world of solutions, wos
Next Thursday you don’t want to miss a live technical webcast with Q&A on the hot topic of Wi-Fi location-based services. Join Techwise tech legend Jimmy Ray Purser and technical marketing engineer lead Darryl Sladden for a deep technical discussion covering the ins and outs of Cisco’s Mobility Services Engine – the intelligence engine in the Cisco Wi-Fi network that enables Cisco Connected Mobile Experiences functionality.
You’ll get a full, hands-on view of four pieces of the solution and see how it all ties into your Wi-Fi network:
- Location detection – how Cisco’s Wi-Fi infrastructure detects mobile devices and calculates their location
- Analytics – how the MSE aggregates and reports Wi-Fi location data and trends to administrators and operations leads so that they can better understand guest behavior
- APIs – how Cisco’s Mobility Services APIs provide application developers rich, contextual information they can use to create a variety of internally and externally-facing apps
- Maps – a use case of how Cisco uses it’s own Wi-Fi location-based services inside the organization to increase efficiency and employees get to where they need to go
This is an in-depth session you won’t want to miss. Register now and mark your calendars for December 12!
Tags: analytics, API, cmx, connected mobile experiences, location, location detection, location services, location-based, map, mobile, mobility, Techwise, 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
Within the coming decade, Internet Protocol version 6 (IPv6) will be key to enabling 50 billion connections among people, processes, data, and things in the Internet of Everything (IoE). But how we get there from here is not a simple matter.
I’m very pleased to invite Mark Townsley, Cisco Fellow and recognized industry expert on IP, to discuss this important transition in the second of our three-part blog series on IPv6. The first blog in Mark’s series was “Demystifying IPv6”.
Three years ago, I organized a conference in Paris where I thought it would be fascinating to bring together the original designers of IPv6 alongside the engineers who were finally deploying it at scale more than a decade later. During this discussion, Steve Deering, one of the “fathers” of IPv6 in the 1990s, was asked one of the most common questions about IPv6: Why wasn’t it designed for backward compatibility with IPv4? After all, wouldn’t it be easier to make the transition if the two versions could transparently coexist? Steve answered that the problem is not that IPv6 wasn’t designed to be backward-compatible—the real problem is that IPv4 wasn’t designed to be forward-compatible.
Steve was making the point that IPv4 was designed with a fixed address space. Given the number of computers connected to the Arpanet throughout the 1970s, this fixed-length address field seemed to be sufficient—at least for that version of IP. IP had been replaced before, and it seemed perfectly reasonable at the time that it might be replaced again. Read More »
Tags: 6rd, Cisco, Internet of Everything, internet of things, internet protocol, IoE, IoT, ip, ipv4, IPv6, IPv6 rapid deployment, map, mapping of address and port