A lot can change in 25 years. At the first Cisco Live (then known as Networkers conferences) in 1989, 200 geeks gathered for the inaugural event. Fast forward to three weeks ago, when we welcomed a whopping 25,000 attendees into the arms of our namesake, beautiful San Francisco.
We heard there was some interest in how the network performed at the show, so I wanted to share some of the interesting statistics about the network at Cisco Live! I shudder at the thought of the ancient network from 25 years ago. So here we go:
Wi-Fi Client Devices
This year we saw 30,705 unique devices, with 7000 in the theater for John Chambers’ keynote.
# of Unique Clients
# of Sessions
# of Unique Users
# of Unique APs
Avg Users per AP
Max. Concurrent Connected Wi-Fi Devices
There was a peak of 14216 concurrently connected device at SF this year.
This week we have two opportunities for you to learn about Cisco technologies from company experts as well as our technology partners.
The first webinar,How Smarter Branches Lower Costs, is on Wednesday, December 11 at 8am Pacific and discusses how Cisco Intelligent WAN (IWAN) along with Akamai’s Unified Performance solution can help your branch offices can realistically utilize Internet as WAN for a cost-effective, reliable, and secure option.
A preview for this webinar is a quick video we did with Akamai in October!
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 »
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 »