Cisco Cisco 3350 Mobility Services Engine Developer's Guide
C
ISCO
MSE
API
S
PECI FICATI ON
G
UIDE
–
C
ONTEXT
A
W ARE
S
ERVICE OF
MSE,
R
EL EASE
7.4
.
P
A G E
26
O F
2 27
CHAPTER 1
1
Overview
1.1 Introduction
This document defines all the APIs available in the Mobility Services Engine.
1.2 Purpose
The goal of this document is to describe the interface to the Cisco Mobility Services Engine and
how client systems may take advantage of the system.
how client systems may take advantage of the system.
1.3 System High Level
What is MSE?
MSE (Mobility Services Engine) is the insertion point for services in the network.
Ability to add services outside elements in the data path (controller/switch) facilitating
Ability to add services outside elements in the data path (controller/switch) facilitating
faster adoption.
– MSE is the integration point for applications through well defined APIs that help
in Asset tracking for location.
MSE becomes the platform for integration between Cisco technologies and partners.
The MSE communicates with the WLAN infrastructure components such as the Wireless LAN
Controller (WLC), The Wireless Control System (WCS) and the Location Server. The MSE gathers
statistics and data of the clients from these components – information such as location.
In a very small network all services could be running on the same box. So based on the scaling
requirements and deployment scenarios a Mobility Service Engine box can contain one to many
services. Services running inside one box can interact with services running on another box.
Controller (WLC), The Wireless Control System (WCS) and the Location Server. The MSE gathers
statistics and data of the clients from these components – information such as location.
In a very small network all services could be running on the same box. So based on the scaling
requirements and deployment scenarios a Mobility Service Engine box can contain one to many
services. Services running inside one box can interact with services running on another box.