connected mobile experience

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1

Agenda• Connected Mobile Experiences

— Overview – What is CMX

• Enabling Technologies behind CMX— Location Analytics

• New Location Planning Guide— Design Considerations— Architecture Considerations— New Location Services Calculator

• Enabling Technologies behind CMX (Cont.)— Mobile Concierge

• Building Location awareness into mobile applications

• Leveraging Indoor Location aware mobile devices


Why Connected Mobile Experiences?

Connected Mobile ExperiencesChallenge

Business and venue operators face increasing pressures from changing business landscape.

Business operators have very limited visibility into their business environment. Where, when and how do people move around the venue?

Challenge Trend

Explosion of Mobile Devices and BYOD connecting everyone, everywhere, all of the time.

WLAN networks becoming increasingly sophisticated enabling new capabilities and services

Trend


Connected Mobile Experiences

GUEST PRESENCE GUEST ACCESS GUEST EXPERIENCE

Customer: Presence in the venue. IT: understand network utilization, peak usage, number and types of devices on the network.

L O C A T I O N A N A L Y T I C S

The customer’s personal mobile device and its characteristics are detected before they enter the venue.

The customer is seamlessly and securely connected to the Wi-Fi network based on their personal preferences and profile, including device type and roaming credentials.

The customer receives highly relevant content and services based on their preferences, profile, and real-time location within the business venue.

Business: insights into customer online and onsite behavior, most traffic paths, dwell times, location density etc.

DETECT CONNECT ENGAGE


Vertical Use Cases

Consumers Guests Passengers

• Context rich promotions

• Informed purchase decisions

• In-store experiences

• Maps with featured attractions

• Happy hour show tickets

• Gift shop promotions

• Staff security to passenger traffic flow

• Flight updates gate directions

• Improve travel experiences

RETAIL HOSPITALITY TRAVEL

• Wayfinding patient apps

• Improved patient experiences

• Medical device location history

• Campus maps directions

• Stadium sales athletic event experience

• Real-time bus maps

Patients

HEALTHCARE

Students

EDUCATION


Connected Mobile ExperiencesHow does the vision map out to Solutions?

DETECT CONNECT ENGAGE

• Presence Detection

• MSE Location Services

• Location Analytics

Mobile App

• Auto On-Boarding

• Hot Spot 2.0

• Lobby Ambassador

• ISE

Mobile ConciergeSDK

Meridian App Editor

Browser(Future)

On Device without

Application 802.11u

/MSAP (QC)

Concierge enables engaging with customers via different media

Different ways to implement app

Mobile Concierge

Cisco Confidential© 2013 Cisco and/or its affiliates. All rights reserved. 6

Advanced Location ServicesNew Capabilities in 7.4


Agenda• Overview

• Licensing Changes & Software Requirements

• Location Analytics (Think Smart Integration)

• Mobile Concierge App Based (Meridian Integration) Device Based (Qualcomm Integration)


Location Services Topology

CAPWAPCAPWAP

CAPWAPCAPWAP

CAPWAP

CAPWAP

CAPWAP

CAPWAP

NMSP over SSL NMSP over SSL

SNMP SNMP

SOAP/XML overHTTP/HTTPS

Third Party Server

Location API via SOAP/XML over

HTTPS

Cisco Prime Infrastructure

Management Station (Client Browser)

HTTPS

Wireless Clients


Connected Mobile Experiences Software Requirements

Platform Min SW versions

Wireless LAN Controller 7.2

Access Point 7.2

Cisco Prime Infrastructure 1.3

Mobility Services Engine 7.4


Location Analytics ThinkSmart Integration

Transforming device positioning information into actionable Business Intelligence


Agenda• Overview

• Enabling Analytics on the MSE

• The Analysis Process

• Reporting Interface

• Verification & TroubleshootingTypical Issues


Overview – Location Data Usage < 7.4• The MSE collects and maintains device location data obtained from Wi-

Fi enabled devices such as smartphones, tablets and laptops as they pass through the Cisco Wi-Fi network, saving it “as is” in the database— The basic data is of the form, <MacAddress, time, coordinates, attribute1...

attributen>

• In previous versions of the Cisco Wi-Fi network architecture, this data was simply retrieved by an API call from the Cisco Prime Infrastructure and used to display device location information to the user via the GUI or in a simple report

• In 7.4 the ThinkSmart Analytics engine has been directly integrated into the Mobility Services Engine— Analytics GUI is served directly from the MSE platform— Shares the same database while using a separate table space


Overview – Location Data Usage > 7.4• Analytics engine uses location information in the MSE database to create new

knowledge about an environment by summarizing activities in terms of:— Areas

— Dwell times

— Paths Taken• Choice of direction

• Routes taken

• When analyzed in ThinkSmart, the location data produces information and knowledge on movement and behavioral patterns on the devices at a specific location, transforming previously underutilized device positioning information into actionable Business Intelligence— Aggregates separate but related pieces of location data: such as client ID, position, dwell time,

etc. into a single data point

— Identifying different types of behavior even in the same building

• An analyzable location can be a shop, mall, airport or a city center, provided that it has a network of wireless access points enabling devices moving within that space to be located


Enabling the Analysis Engine• Although the ThinkSmart Analytics engine is installed on the MSE during

the 7.4 software installation process, it must be enabled for use via the PI before the Web interface is accessible.— Requires an Advanced Location Services license for MSE


Network Preparation• In addition to licensing, before analytics visualization and reporting is

available floor plans and coverage areas must first be defined in the PI and synchronized with the MSE

• A coverage area in the MSE correlates to a zone for the purpose of analysis— A zone is a user defined space with a name and can be used for reporting

or path description purposes; zones can be overlapping and need not cover all the building

— For example: If a customer wants to analyze user behavior within a specific area of a location, such as an individual store within a larger mall complex, then a coverage area defining that store must be defined in the PI.


Refining the Data source• As analytics information is derived directly from the device positioning

information in the MSE database, it is only as accurate as the information contained in the MSE database— To obtain the most accurate information the Wi-Fi network contributing

location information to the database must be deployed in accordance with Cisco best practices for location awareness

• By default the analysis process takes in location data for all networks, buildings, and floors defined in the Prime Infrastructure— If all floors are not location ready or the customer only wants to analyze data

from a specific network or specific parts of the network then the mse.properties file must be edited

# Notice that an empty list means to include all.#Networks=#buildings=#floors=#


Device/Path Database Creation• The process of downloading and creating the Devices/Path database is

automatic— For a fresh install data collection begins immediately

• MSE database data polled every 15 minutes by default

• Analytics available after first 15 minutes passes

— For an upgrade to an existing MSE which has been collecting data, then Location Analytics will download the last 3 days of data

• MSE database data polled every 15 minutes by default

• Analytics are available immediately since data is in the Location Analytics database

• Analytics processing on the MSE can impact performance in two ways— Polling frequency: trials have shown this to be negligible on a polling frequency of

every 15 minutes

— Size of the dataset to be processed: analytics have been optimized to work only on a sample of the data if too large a dataset is requested 256K max. Over that it starts sampling


Cisco Analytics Architecture

Thinksmart AnalyticsEngine

DataMediation

MSEDatabase

Device/PathDatabase

WLC Location

Data

Reporting

Graphical UserInterface

ResultsDatabase

Location

Data

Floor plans& zones

JBoss ApplicationServerMobility Services Engine

MSE Location Analytics Architecture for Release 7.4

Reports

Automatic conversion of data to results on: dwell, device no., movement, frequency


The Analysis Process• Full data analysis is comprised of six individual processes:

— Data cleaning— Tagging— Filtering— Parameter estimation— Behavior mining

• By combining these processes the system can handle very large amounts of data that can be correlated and analyzed to summarize activities, which allows us to both visualize the data and output it in a report format as well

• The ability to visualize the results in both 2D or 3D formats provides the user an improved understanding of the results— This is especially true in a multi-story environment where paths and dwell

times must take vertical movement into account


Accessing the Analytics UI• Open a WEB browser and navigate to http://<mse_IP_address>:8080/ui

Default login is:Admin/Adminalthough any username configured on the MSE will work


Visualizing the Data• Both 2D and 3D views are available, with 3D as the default

3D building representation requires using a browser that supports WebGL

Note: Not all browsers support WebGL on all hardware

Ideally the hardware would have a

3D graphics card to

ensure compatibly with WebGL

Birds-eye or Overhead view


Browser Verification• Test your browser for suitability at http://get .webgl.org/

— If this is successful, you should see a WebGL rotating cube— If the support is not there, it may be possible to update your video driver

For Firefox, confirm suitability by going to: Help->Troubleshooting Information, then scroll down to Graphics and WebGL Renderer. This will indicate if your system can support WebGL and if not what is recommended.

For Chrome, follow: http://support.google.com/chrome/bin/answer.py?hl=en&answer=1220892


Intro to the Analytics UI• Analytics View with default building

Analysis Control Panel

3D Result Visualization Area


A Better Analytics UI For Outdoors• Two Dimensional Analytics View with Open Street Maps

2D Result Visualization Area

Identical Analysis Control Panel


Analysis Control Panel• Allows the customer to define the type of analysis they want to carry out

and on what subset of devices, such as date, time, zone, etc.

Rule types to specify which devices are considered in the

analysis

Start the analysis

Type of analysis to conduct

Building to conduct the analysis on

Switch between analysis and reporting


Defining a Rule Set• A number of rules together is called a “rule set”

— These can be saved and loaded to repeat the defined analysis criteria

In order to describe the subset of data, parameterized rule types have been created. • The rule around date presents the user with

valid dates of location points in the database.

• The time rule allows the user to specify any hour/minute within 24 hours.

• Rules on paths identify devices with possible start, finish and/or intermediate points on a path


Navigation and Information Panel• The panel in the upper right-hand corner provides navigation, view, and

parameter selections

Point, Orbit, Pan and Zoom controls

Select 3D viewSelect 2D view or

overhead perspective

Result Visualization controls

Parameter SelectionAdditional

Information


Interface Navigation Demo• Analytics UI is reached at http://your.mse.ip.address:8080/ui


Accessing the Reporting Functions• q

Selecting the Reporting button within the Analytics Visualization view takes you to the Report Generation view


Available Reports• With this release of analytics processed on the MSE we are limited to

five pre-canned report options


Focusing the Report Output

• Although reporting is limited to pre-designed formats, each report can still be customized to focus the output to a smaller data set.


Report Output Format• Once a report is run the results are returned as a downloadable .pdf file


Typical Issues – What to Check First• No UI displayed at all

— Verify no firewalls are blocking access to port 8080 on the MSE— Verify the application is accepting connections on port 8080

• Try connecting using telnet. Notice it does not necessarily accept connections on localhost; try the ip of the machine instead

• “Loading 3D Environment” does not disappear or message appears saying 3d environment cannot be loaded because there is no data— Verify browser is webgl compatible - http://get .webgl.org/

— Verify that the MSE has floor plans for the floors that are in the analytics DB

— Verify enough time has elapsed for the first data to start appearing in the analytics db; this can take 90 minutes or more

— Verify that data is being collected by the MSEclient (mse.log)• Also check that the data is being sent correctly to the analytics server (there should be

messages like 'Sent XX paths, YY points (avg: YY/XX points/path),ZZ zones.' in that file)


Typical Issues – What to Check First• Analytics error message “relax criteria”

— No data was found for the specified set of filters. Try to relax the filter to see if that makes the message go away

• Analytics error message “using sample”— Too much data was found for the specified set of filters. 250k points have

been taken into account for the analysis shown. Currently, there is no way to override this.

• Internal server error — Go straight to opening a TAC case

• Points not appearing where expected— Verify AP placements on Prime Infrastructure maps are correct— Remember mse client also caches floor plan information, for up to 4 hours


MSE 7.4 Wi-Fi Location Based Services Planning GuideUnderstanding Location Services Impact on Network Design Decisions


Agenda• Planning Guide Overview

• Architecture and Planning Considerations

• Best Practices

• Location Services Calculator (Bandwidth, Transaction rate (TPS), Storage, Accuracy, and Currency)

• Location Services Calculator Demo

• Resources


Location Based Services Planning Guide Overview• Guidelines to provide deployment flexibility, more comprehensive

planningE.g. Location accuracy/currency, bandwidth and MSE server compute requirements or Transactions Per Second (TPS)

• Location accuracy – delta between estimated and actual location

• Location currency – elapsed time between location estimates

• Bandwidth and MSE transaction rate considerations— Client type (each probe results in a measurement made by the WLC &

reported to MSE affecting currency of location estimate)— Client mobility (each roam/handoff results in a measurement)— APs/Client per WLC (measurement and other reports are aggregated by the

WLC)


• Wi-Fi AP measures and reports RSSI (Receive Signal Strength Indicator) to WLC

• WLC (unified/Flexconnect) aggregates and periodically reports them to MSE via NMSP

• MSE applies advanced positioning algorithms

• Determine location (RF fingerprinting/modeling)

• Location notifications (e.g. to Meridian)• Statistical processing for Location

Analytics• Displaying all devices on a map in CPI

Location Based Services Architecture

Cloud-basedapplication(e.g. Meridian)OpenAPI

(SOAP/XML)

NMSP

Mobility Services Engine (MSE) w/Mobile Concierge & Location Analytics

Wireless LAN Controllerunified or FlexConnect

Wi-Fi Access Point(AP)

Wi-Fi Access Point(AP)

Wi-Fi Client Wi-Fi Client

Cisco PrimeInfrastructure

Intra/Internet

LAN orWANSOAP/

XML


General Architecture ConsiderationsCo-located(AP, WLC & MSE in the same LAN)

Partly Distributed(AP on LAN, WLC & MSE remote)

Fully Distributed(AP & WLC in the same LAN & MSE remote)

Location application

In-house E.g. corporate HQ Server Cloud based E.g. Meridian Cloud based E.g. Meridian

MSE MSE+WLC per site E.g. campus MSE+WLC per DC E.g. retail HQ MSE per DC E.g. Regional HQ

WLC MSE+WLC per site E.g. unified WLC

MSE+WLC per DC E.g.Flexconnect WLC

Unified WLC per site E.g. property/venue

Bandwidth considerations

Insignificant (links >=100Mbps vs. LBS traffic <1Mbps)

Significant (MSE & app server link ~ T-1 vs. 5Mbps for 100K client for northbound API)

More Significant (MSE & App server link + WLC & MSE link ~T-1 vs. 1.5Mbps for 10K client for NMSP traffic)

TPS considerations

Over 1000 TPS for 100K client per campus/venue

Over 1000 TPS for 100K client per venue

Over 1000 TPS for 100K client per venue

Cloud-basedlocation application(e.g. Meridian)

MSE per data center(e.g. Regional HQ)

Unified WLC per site(e.g. property/event)

Internet(e.g. T-1)

WAN/Intranet (e.g. T-1)

GigE LAN

Cloud-basedlocation application(e.g. Meridian)

MSE+WLC per data center(e.g. Retail HQ)

e.g. FlexConnect WLC

Internet(e.g. T-1)

WAN/LAN

GigE LAN

In-house/ITlocation application(e.g. corporate HQ)

e.g. Unified WLC

Intranet(e.g. OC-1)

GigE LAN

GigE LAN

MSE+WLC per site(e.g. Campus)Flexible MSE

deploymentoptions


Advanced Location Based Services(Mobile Concierge)• Bandwidth considerations

— BW between MSE and Meridian servers— BW between WLC and MSE

• Computing cycle considerations— Transaction rate of MSE (Each

location/zone based location updateis a distinct SOAP/XML transaction)

CoreApp

Mon

itorin

g &

Rou

ting

SDK

Sent to Meridian Cloud- Location Notifications- Map data

Calls to Meridian- Get map Data- Get Current Location

Response from Meridian- Map data (images)- Current location (x,y, time)

Client App

All other d

ata to/fr

om App

- App data

Positioning information

(MSE detects device & location)

Cisco MSE

Cisco WLC

Meridian/Cloud-basedLocation Server

App Server

Considered in planning guide/calculator

Not considered in planning guide/calculator

MSE compute cycles


RF planning for Location Based Services

Use case Event Action

Presence user enters building/store

send welcome message form Mobile Concierge

Proximity user is close to product display

send advertisement

Asset-tracking devices/tags has moved outside area

alert loss prevention

Mobility/path tracking

Subject movements Location Analytics updates

Zoned(Geo Fenced)

Un-zoned

RF Network supports such applications based on expected accuracy and currency.


Location accuracy/currency examples• Accuracy: function of AP density & AP height

• Currency: function of AP density and client type (client probes network at different rate)

Application Venue type AP density Avg. Accuracy Currency

Presence Mall, airport … 10+K Sq ft 30ft N/A

Proximity Retail … <2.5K Sq ft 15ft ~30s

Asset-tracking Enterprise, mall … 5K Sq ft 20ft >> 1min

Mobility-tracking Mall, airport … <2.5K Sq ft 15ft ~30s


Average expected accuracy examples

CUWN with an average of2500 – 5000 sq. ft cells

5 – 7 meter


Total location error

Movement error(currency)

RF Uncertainty

Client speedUncertainty

Estimation error(accuracy)

uncertainty in exact RF propagation loss between the client and the AP

uncertainty on speed of the user since the client device reports position periodicallyInitial position estimation error

+ Movement error

TOTAL LOCATION ERROR


Designing Location Services - Best Practices • Based on accuracy and environment type (office vs. indoor high-

ceiling), the density of APs (average cell-radius) can be determined and maintain average cell-radius throughout the service area on each floor.

• Plan for location (e.g. using the PI planning tool)— Design for good coverage first (RSSI of >= -85dBm on all channels clients

support)— Design for good cell-edge delineation (i.e. ensure client roams between adjacent

cells)— Each client should be within convex-hull of 3+ APs on the same floor — Place perimeter AP’s first then place interior AP’s to minimize coverage gaps — Staggered AP deployment (not in a straight line) [esp. in long narrow coverage

areas like hallways, corridors, tunnels, etc]

• Use location rails, exclusion regions, and inclusion regions to constrain the location prediction to valid areas of the map with the PI Map editor.


Designing Location Services - Best Practices • Characterize the CUWN RF environment either using the pre-

canned RF Fingerprinting models (preferred) or via RF calibration (measurement) followed by a location accuracy assessment.

• Four default pre-packaged RF models are provided with PI:— Cubes & walled offices— Drywall office only— Outdoor open space— Indoor high ceiling

• If the provided default RF models do not sufficiently characterize the floor layout, custom calibration models can be created using PI and applied to the floor to better represent the RF characteristics of a given environment.


Designing Location Services – Access Point Deployment Considerations• Proper placement and density of access points is critical in achieving the

quoted location tracking performance— Original design may have been based on coverage model

— Evolving needs may require a different AP-deployment model

• Access Point Density recommendations— Use smaller, overlapping cells (lower data rates disabled)

— For wireless data only deployments: 10% AP cell overlap

— For wireless data + voice deployments: 20% cell overlap

— AP density [Cell radius/area] 28ft/2500sqft – 40ft/5000sqft

• Antennas should be oriented horizontally (vs. vertically) • Antenna diversity should be enabled (ClientLink not relevant for location)


Advanced Location Based Services(Location Analytics)Location Analytics Application (LAA): co-located with MSE

• LAA shares DB with MSENo additional BW needed between MSE & WLC

• background task ran infrequentlyNo compute resource impact

• DB schema distinct from MSE• Estimated DB storage is

200MB/million points• Number of points =

#_clients * duration_in_days *(#_location_reports_per_client_per_day + #_zone_crossings_per_client_per_day)


Location Services Calculator• Calculates MSE BW and TPS Due

to location tracking & location alerting (LT & LA)

— Based on rate at which client roams between APs and

— Rate at which client enters/exits user defined zones.

— Above rates are estimated based on network topology (e.g. client, AP density) Venue type (e.g. retail, office) and building dimensions (floor size, number of floors …)


Location Services Calculator• Inputs:

client types,network nodes in volume(# clients, # AP, # WLC) or density(sq.ft/client, sq.ft/AP),venue type and building parameters(sq.ft/floor, # floors).

• Outputs:NMSP Bandwidth per WLC (bps)NMSP Bandwidth per MSE (Mbps)SOAP/XML Bandwidth per client (bps) [due to both LT and LA activity]SOAP/XML Bandwidth per MSE (Mbps) [due to both LT and LA activity]MSE Transactions per MSE (TPS) [due to both LT and LA activity]Accuracy (ft) Currency in distance (ft) and time (s) Incremental Location Analytics storage (GB)


Location Services Calculator – BW, TPS, Storage, Currency and Accuracy

Bandwidth

TransactionsStorageCurrencyAccuracy

Samsung Tab (small)Samsung Tab (large)Samsung PhoneIntel PhoneApple iOSIntel LaptopGeneric (mix)

Client Access Point Controller Physicalaspects

OfficeRetail


Mobile Concierge – App BasedMeridian Integration

Engaging the customer


Overview• According to the dictionary a concierge is:

— A person who has charge of the entrance of a building and is often the owners representative

— A doorkeeper who permits or denies entrance on behalf of the owner— In hospitality, one who can obtain items or services for you

• The WNG Mobile Concierge is a collection of protocols, services, and partnerships which assist with or automate a wireless clients connection to the network and provides better indoor navigation capabilities— Allowing business to engage users through a native app on a smart mobile

device

• In 7.4 the partnerships include:— Qualcomm Partnership— Mobile Concierge SDK – Meridian Partnership— Other partners will be added to our ecosystem over time


Meridian Partnership• The goal of the Cisco Meridian partnership is to simplify a Venues ability

to provide location-based services to users without requiring them to connect to the network and access the MSE directly

• Through this partnership a Cisco customer is provided the capability to:— Either add location awareness to their existing mobile app, or quickly build a

cross platform location enabled app from the ground up• Apps can show a visitor their location, provide turn-by-turn directions, or enable

Location-Based Offers - All driven by wireless client position notification from the MSE using our existing SOAP/XML API


Meridian Integration• Meridian is integrated into an existing

WLAN by:— Using location update and containment

events from the MSE to show the location of a mobile device in a mobile app and deliver push notifications

— Meridian provides an online content management system to create placemarks, mobile app content and routing for turn-by-turn indoor navigation

— Meridian provides and supports both mobile app creation and branding capabilities along with an SDK for iOS and Android devices to enable integrating location capabilities into an existing mobile apps.

Meridian

NMSP

MSE

WLC

Get

Loc

atio

n

Push N

otification


Mobile App Integration in Action• By defining containment zones within the Prime Infrastructure map subsystem

push notifications can be sent to a device when it enters or leaves an area— Location enabled Apps show the device location using the location update events and

can provide turn-by-turn indoor navigation

— To push all MSE CAS notifications and update events, the MSE and Prime Infrastructure must be on a routed subnet and configured for DNS resolution using servers capable of resolving the Meridian App cloud server URL


Defined Coverage Areas Trigger Notification• In order to have user location change triggered in Meridian App

coverage areas and location regions must be configured for all the zones that require a notification sent to the client device


Mobile App Enablement• Enabling this integration will allow the MSE to send floor maps and

wireless client position notification to Meridian

✓


Mobile App Enablement (Cont)

The name you enter here will appear in the Meridian app as the location/venue name

Meridian will e-mail these addresses with instructions on how to

access the Meridian online editor and SDK and share it with

others in your organization

Select defined coverage zones here

Selecting Save causes the MSE to generate an http post command to the Meridian Servers for account generation and synchronization


Mobile App Enablement (Cont)• Meridian will return an email allowing the acceptance of an invitation to

complete the account activation process and download the SDK from

Link to complete activation processLink to download the iOS or Android SDK

Information on which Campus, Building and Floor information that has been transmitted to the Meridian servers


Infusing Your Existing Mobile Application With Location Capabilities• Follow the emailed activation link to create your login credentials

Note - Meridian currently only supports the Chrome and Safari browsers for accessing their Website


Infusing Your Existing Mobile Application With Location Capabilities (Cont)• p

Only the BlueDot Kit Trial (SDK) is available on your initial login

Access to the online Editor and App builder requires a separate upgrade request be sent to Meridian after you complete your initial login


Obtaining the SDK• Download the appropriate SDK to create the necessary binaries which

will enable your existing App to contact the Meridian Cloud servers at http://dev.meridianapps.com/docs/downloads


View MSE Clients Online through Meridian

1

2

3

4

View the Clients known to your MSE in real time and watch them update as their positions change

Upgrade your account to receive a 60 day free trial of the Editor features


Getting Access to the Editor to Add Turn-by-Turn Navigation to Your Application

12 3

45


Adding Place marks and Routing


MERIDIAN SDK Support ResponsibilitiesI. SUPPORT RESPONSIBILITIES AND PROBLEM SEVERITIES

A. Support Responsibilities.

1. Cisco Support team is not responsible to support or debug Company’s Product or development related queries.

2. Cisco support team will use reasonable efforts to provide the Company’s technical support contact information if the problem is not associated with Cisco MSE location service software license.

3. Cisco Support team may at times escalate issues to Cisco Development Engineering Group (“Cisco DE”). Cisco DE may contact Company’s Development Engineering Support Group or its equivalent (“Company DE”) for consultation or support in relation to investigation of escalated issues. Company’s and Cisco’s contacts are listed in Appendix A of this Exhibit. The Company DE shall provide support and communication as defined by the support and severity level definitions below with regular updates to the Cisco DE with respect to the case progress. In the event that diagnostics and troubleshooting are required at an End User site, Company supports the End-User per the Company and End-User support agreement

• Meridian support contact is [email protected]

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 68Cisco ConfidentialCisco Confidential© 2013 Cisco and/or its affiliates. All rights reserved. 68

Mobile Concierge – Device BasedQualcomm Partnership


For the Client: Qualcomm Partnership• Two distinct parts to our Qualcomm partnership:

— Indoor navigation using infrastructure assistance• MSE – Qualcomm integration

—Mobile Service Locator service integration• Embedded MSAP client in Qualcomm Chipset

• MSE – Qualcomm integration aims to provide mobile devices with Qualcomm (Snapdragon) chipsets better indoor navigation capability.— Achieved by combining location and infrastructure information about

a floor available with MSE (position of access points , GPS markers etc.. ) with the floor geometric feature information (position of walls , doors and other points of interest)


Qualcomm Partner Discovery Server (PDS)• Position of walls , doors and other points of interest are

extracted from a CAD file by the Qualcomm Map Extraction Tool (MET) and provided to Qualcomm’s Partner Discovery Server.

• The PDS generates encrypted assistance data using the floorplan and AP data provided by MSE for use by mobile devices. — Encrypted assistance data and AP data is returned to MSE for

storage

• PDS also communicates with handsets to help them find MSEs quickly when a user approaches a venue— Distributes the decrypt keys to trusted mobile devices


MSE – Qualcomm Integration Prerequisite• Venue Admin first collects the CAD maps of his venue

— Then opens the QC MET tool and loads the CAD maps— Selects and edits the layers required saving output as a zip file containing:

• Image file (.PNG format) to be used as floor Map on NCS

• Span.xml file containing the dimensions of the floor (horizontal and vertical) in meters

• Qualcomm specific map XML file containing geometric feature information related to walls , doors , Points of Interests etc


MSE – Qualcomm Integration• Admin logs into the MSE and navigates to Floor map creation page

— Imports the zip file that was created by the MET tool— Visually verifies that all the details are correct, and completes the floor

creation by: • Placing APs on this floor and setting up GPS markers

• Cisco Prime Infrastructure (CPI) synchronizes the new floor information to MSE


MSE – PDS Synchronization • Once the MSE is synched with the CPI, admin manually initiates a synch

between the MSE and PDS by triggering what Qualcomm calls an F2 interface request— F2 interface requests is accomplished using the MSE cmdshell

— Must be repeated each time a major change is made to the floor information


MSE & Phone Roaming Interactions • As the user leaves the current floor and approaches a new floor, the

phone fetches assistance data for the new floor (if it doesn’t already have them) from the MSE and goes through the decryption process again — The phone might need to fetch decryption key for the new floor from PDS, if

it already doesn’t have them

• If the same phone returns to the venue a few days later, there is no need for the phone to fetch assistance data from the MSE again; it can use the cached assistance data that exists on the phone— subject to the condition that it hasn’t expired

• As the user moves around at the venue, the phone computes the its location in real time without communication with the MSE— The phone will only contact the MSE again when it needs assistance data

for a new floor


Enabling MSE – PDS Integration • MSE – PDS Integration is enabled and configured from PI Lifecycle View

Navigate to Design>Mobility Services Engines><MSE name>>System>Qualcomm PDS Configuration

Select here to enable MSE-PDS Integration

MSE name must be resolvable in the DNS server assigned during network connection

SSID returned to mobile device by PDS server for MSAP attachmentUsed to configure the

validity timeframe for the assistance data before requiring refresh


Qualcomm MSAP Client Operation Non-Location Assistance • Mobile devices using the Qualcomm Snapdragon chipset will have a

built-in MSAP client which will communicate with the MSE to fetch Service Adverstisements and make them available to the user

Qualcomm based mobile device enters the venue

Embedded MSAP client tries to detect support for MSAP using the beacons coming from the APs

If the phone finds MSAP support in the beacons, it will try to find the MSAP server hostname (the MSE hostname) from the DNS SRV record Once the MSE hostname is

resolved the MSAP client on the phone communicates with the MSAP service to fetch all available Service Advertisements

DNS Services

Mobility Services Engine

Wireless LAN Controller

1

2

3 4


Mobile Concierge Service• The Mobile Concierge service allows the venue owners and service

providers to deliver a unique in-store experience to their end users; customers who are using smart phones that have been configured with a set of policies for establishing network connectivity – opt in— Once connected to the stores Wi-Fi network the Mobile Concierge service

facilitates smart devices to discover available network-based services.— These services can include the ability to organize shopping lists, make

product suggestions, update customer loyalty data and receive electronic coupons or promotional offers identified by their unique digital signature based on shopping preferences.

• To accomplish this The following must be defined:— Venues— Providers— Policies

•


Mobile Concierge Venue Definition• The Mobile Concierge Venue defines the boundaries for advertised

services


Mobile Concierge Provider Definition• Main purpose here is to tie the provider together with the Icon to be

displayed on the device to represent the provider

Defines the Service name associated with Icon served to the handset

Identifies the type of device the defined URI is intended to operate on

Defines the OS the defined URI is intended to operate on

Identifies App location – On the Device or on the WEB

Defines the loyalty App recommended for the venue

Icon files must be ≥ 8Kb with 4Kb or less preferred


Mobile Concierge Policy Definition• A policy defines on which SSIDs and at which locations within a Venue

that a service/s will be advertised

Default setting

Multiple services on multiple SSIDs can be configured within the same policy


For More InformationCisco Documentation

• Cisco Prime Infrastructure Configuration Guide for Software Release 1.3

• Connected Mobile Experiences Deployment Guide using Cisco Mobility Services Engine (MSE)

Via the Web

• CMX External Web www.cisco.com/go/mobileexperiences

• Cisco Internal Webhttp://iwe.cisco.com/ws#web/view-post/post/-/posts?postId=340700223

For any inquiry –

[email protected]

http://www.cisco.com/go/mobileexperiences

http://iwe.cisco.com/ws

http://iwe.cisco.com/ws

mailto:[email protected]

connected mobile experience

Technology