Cisco Cisco 3365 Mobility Services Engine 白書

Page 6 of 55

●

Context Aware Service (also called Base Location Service): Calculates the X,Y location coordinates of

devices based on antenna patterns and received signal strength indication (RSSI) and enables the Cisco

MSE API

●

WIPS: Provides a wireless intrusion prevention system (WIPS) for wireless-specific network threat

detection and mitigation against rogue applications, malicious attacks, and security vulnerabilities

●

CMX Device Engage (also called Mobile Concierge Service): Enables connectivity with end devices that

support Cisco Mobility Services Advertisement Protocol (MSAP)

●

CMX Analytics: Provides summary information about the movement of devices within the venue

●

CMX Browser Engage: Enables creation, management, and transmission of content to visitors’ web

browsers

●

HTTP Proxy Service: Provisions the HTTP proxy server for the CMX Browser Engage service

These services may be referred to slightly differently in different documentation. Table 1 lists the various names of

the processes.

Table 1.

Cisco CMX Service Name Variations

Technical or Traditional Name

Cisco CMX Marketing Name

User Interface Name

Context-Aware Service (CAS)

Base Location Service

Base Location (Context Aware Service)

wIPS

WIPS

Mobile Concierge Service (MSAP)

CMX Device Engage

Analytics

CMX Location Analytics

Guest Portal

CMX Connect

CMX Connect requires that the CMX Browser Engage box be selected

Billboard (BBX)

CMX Browser Engage

BBX Proxy

None

CMX Browser Engage HTTP Proxy Service

Configuring Cisco MSE for Cisco CMX Location Analytics

Cisco CMX Location Analytics uses all input from Cisco MSE. It is installed as part of the Cisco MSE installation,

but it needs to be explicitly enabled, by selecting Locational Analytics in the list of enabled services in Cisco

Prime

™

Infrastructure. If the user wants to use only data from specific parts of a network, then the user needs to

edit the mse.properties file (opt/mse/analytics/intellify/tools/MSEclient/mse.properties) to select the network,

building, and floor to be analyzed. If the default configuration is used, then the entire network is available for

analysis.

Tip: If you have a very large venue and want to reduce CPU load, you can specify fewer areas for analysis by

editing the mse.properties file.

Cisco CMX Location Analytics requires both floor plans and coverage areas inserted through Cisco Prime

Infrastructure for the visualization and reporting functions to work. For each floor plan, you also need floor

numbers. Floors on the same level should have the same number; higher-level floors should have higher

numbers. The coverage areas correspond to the zones for which the user wants reports. Therefore, if you want to

know what is happening in location A, then you should create an area delineating that location in Cisco Prime

Infrastructure and name it as such. Zones, and hence areas, can overlap.

Tip: Plan your zones in advance. Make sure that you have enough zones to identify areas of interest, but do not

make your zones too small or they will not contain sufficient data for useful analysis.