Connected mobile experience

3,767 views

Published on

Connected mobile experience
Wed 21st Nov 11:00am - 11:40am

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,767
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
132
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Retail BenefitsIncrease revenue by giving customers relevant promotions based on contextIncrease customer satisfaction through indoor wireless access to aid in purchase decisionEnhance in-store experience by using location analytics to optimize store layoutHospitality BenefitsIncrease revenue through personalized 3rd party advertising and upsell campaignsIncrease customer satisfaction through indoor wireless access and personalized mobile experienceTransportation (i.e. Airports) BenefitsIdentify high traffic areas that could be better utilized Analyze which displays or promotions are effective through dwell timesAssign effectiveness to 3rd party signage based on viewership
  • In order to achieve the best results from the new services being introduced with 7.4 the underlying WLAN must be properly deployed with location in mind. However, even an installed WLAN which is not deployed in accordance with the Best Practices for AP count and placement for a Location enabled network will still be able to utilize these new services. There is a new deployment guide being published which addresses the new concepts of accuracy, and currency. We are most concerned about accuracy in the physical deployment as it is effected by the number and placement of APs.
  • Although not normaly requiring adjustment, both the polling interval and the size of the dataset requested can be adjusted in the opt/mse/analytics/intellify/tools/MSEclient/mse.properties file
  • The rules section allows the user to identify the specific set of devices to which to apply the analytics. In order to describe the subset of data, parameterized rule types have been created. Therefore, 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. A number of rules together is called a “ruleset”.
  • The rules section allows the user to identify the specific set of devices to which to apply the analytics.
  • Fundamental to the Cisco Unified Network (CUWN) is the WiFi access point (AP) which, in addition to serving clients, measures and reports the RSSI in real-time to it’s controlling Wireless LAN Controller (WLC), either Unified or FlexConnect, which aggregates and periodically reports these measurements to the Mobility Services Engine (MSE) via the Network Mobility Service Protocol (NMSP). The MSE applies advanced positioning algorithms to determine location (based on RF Fingerprinting/modeling), dispatches location notifications as needed (e.g. to 3rd-party applications such as Meridian Mobile Concierge) and stores them for statistical processing (e.g. by Location Analytics). The PI displays this location on indoor map and provides seamless management of all CUWN elements (AP, WLC, MSE, etc).
  • In the co-located architecture, the BW available between the elements is typically >= 100Mb/s (i.e. Ethernet) and is very large compared to typical LBS traffic (usu. < 1Mb/s) so we can usu. ignore the additional BW. However, the MSE transaction rate, transactions-per-second (TPS), needs to be considered as this is a function of client-type and mobility (e.g. employees, customers) and may reach >1000 TPS (e.g. 100K clients per campus or venue) and is significant load for the Oracle DB-based MSE application mandating additional MSE appliances. In the partly distributed architecture, the BW available between the MSE and application server (cloud) is typically limited (e.g. T-1) and so the SOAP/XML API traffic must be considered. For example, an MSE at a data-center that aggregates location services for many sites (e.g. 100K clients) may oversubscribe the WAN link simply from its northbound API traffic (e.g. 5Mb/s) mandating an upgrade in the Internet/WAN SLA. In addition, this same application would generate significant MSE TPS as above. In the fully distributed architecture, the BW available between the WLC and MSE is also limited and so the NMSP traffic must be considered. For example, a WLC at a remote site that supports a single venue (e.g. 10K clients) may over-subscribe its WAN/Intranet link from just NMSP traffic (e.g. 1.5Mb/s). In addition, this same application would generate significant MSE TPS as above.
  • A typical in-building LBS venue is shown.In this venue, some areas (green/purple) are marked as areas-of-interest (zones) for the purpose of presence or proximity determination where as the rest of the venue is un-zoned for general asset or mobility/path-tracking.
  • The RF network can support above applications based on the expected accuracy (delta between estimated and actual location) and currency (time between location estimates) required. The accuracy is a direct function of the AP density (& AP height) while the currency is a function of the AP density & client-type (since each ‘probes’ the network at a different rate). Currency is not applicable to Presence application since it does not have multiple location estimates as others.
  • New AP planning: Prime’s RF planninghttp://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bba943.shtml#wireless).Existing deployments: expected accuracy from Context-Aware Service Configuration Guide .http://www.cisco.com/en/US/docs/wireless/mse/3350/7.0/CAS/configuration/guide/msecg_ch7_CAS.html)
  • A typical RF calibration consists of a walk-around of the target environment with a mobile device and allowing multiple AP’s to sample the RSSI of this device. In order to account for environmental variations, many data samples are recorded for a calibrating device during the calibration process.Consideration should also be given to areas of mixed RF attenuation (e.g manufacturing or warehouses) where there might be stacked goods or dense obstruction in one area of the building and/or open spaces used for assembly or shipping. These areas should be treated as independent zones therefore restricting calibration to the areas where highest accuracy is required. If highest accuracy is required for all of these zones in a mixed area then it is possible to break the floor area into individual maps and apply separate RF models but at the cost of inaccuracy at the cell or map boundary
  • Other protocols and services also include802.11u for advertising available servicesHotspot 2.0 for seamless client onboarding to the networkMSAP for push notifications and service delivery
  • The MSE and NCS must be on a routed network so it can access and resolve DNS of www.meridianapp.com so the MSE can push all the MSE CAS notifications using port 80 http to Meridian App cloud server Data bandwidth required for for each wireless client position or zone notification from the MSE to the Meridian Cloud server can be up to a maximum of 1MB/second.
  • MSE software release 7.4 automates the Meridian account creation process by sending an http POST command to the Meridian servers @ edit.meridianapps.com/api/mse/setup so manual account creation is no longer a requirement.
  • The final Master Marketing Agreement will also contain the names and contact information for Meridians DE’s
  • Position of walls , doors and other points of interest extracted from a CAD file by Qualcomm the Map Extraction Tool (MET) and provided to Qualcomm’s Partner Discovery Server.
  • The Map Extraction Tool (MET) is a desktop application that will accept an indoor map (DXF File) of a venue and after some user input generates QC Map XML and a PNG image that captures the geometric features for walls and doors and POIs such as room numbers. Apart from it, it also generates span xml providing horizontal and vertical span of the floor.
  • The venue admin is the individual responsible for determining what level of information (doors, walls, furniture etc.) that needs to be visible on the floor maps for their locationThis could be the individual responsible for administering the MSE, or it can be a separate individual altogether.
  • When importing the MET tool zip file output to the PI during the floor creation process the dimensions (vertical and horizontal) of this new floor will be based on the span xml file generated by MET tool and contained in the zip file.
  • From the Select a command drop-down list, choose Define New Venue and click Go. The Venue Wizard page appears.Enter the venue name in the Venue Name text box and click Next.In the Floor/Outdoor Association group box, you can configure the following: • From the Area Type drop-down list, choose the area type where you want to display the service advertisement. The possible values are Floor Area and Outdoor Area. Note The Building, Floor Area, and Coverage Area drop-down lists are displayed only if you select Floor Area as the area type. From the Campus drop-down list, choose the campus name where you want to display the service advertisements. From the Building drop-down list, choose the building name where you want the advertisements to appear. From the Floor drop-down list, choose the floor type. From the Coverage Area drop-down list, choose the coverage area within the floor. From the Outdoor Area drop-down list, choose the outdoor area where you want to display the service advertisements. This field is displayed only if you select Outdoor Area as the Area Type. Click Next. The Audio group box appears.From the Audio group box, click Choose File to browse and select the audio file to play the audio notification.Click Next. The Icons group box appears. From the Icons group box, click Choose File to browse and select the icon that you want to display on the clients handset. Click Next. The Venue Apps group box appears.From the Venue Apps group box, choose the venue app on which you want to display the service advertisement from the Web App drop-down list.Click Next. The Additional Venue Information group box appears. From the Additional Information group box, you can provide any additional information that the venue would like to provide to the mobile application. You can configure the following: Enter the location detail in the Location Detail text box. This provides details such as store address, zip code, or street address of the venue. Enter the GPS latitude and longitude of the venue in the Latitude and Longitude text box. This helps the applications to identify the venue accurately. Enter any other additional information that the venue would like to provide to the mobile application in the Additional Information text box. Click Save. This information is applied to the MSE and the synchronization happens automatically
  • Enter the providers venue name in the Provider Name text box. Click Next. The Icons group box appears. From the Icons group box, click Choose File to browse and select the icon that you want to display on the clients handset. Click Next. The Local Services group box appears. From the Local Services group box, do the following: • Click the blue inverted triangle icon location at the left side of the Local Service # name to expand the Local Service and configure the following: –  Choose the service type from the Service Type drop-down list. The possible options are: Directory Info, Sign Up, Discount Coupon, Network Help, and Other. –  Enter the display name in the Display Name text box. –  Enter the description in the Description text box. –  Choose the service URIs from the drop-down list. –  Recommended Apps - recommended application for the venue. Click Save.
  • Choose the venue on which you want the policy to be applied from the Venue drop-down list. Click Next. The Provider group box appears. Choose the provider from the Provider drop-down list. Click Next. The SSID group box appears. From the SSID drop-down list, choose the SSIDs on which you want to broadcast the service advertisements and click OK. You can choose multiple SSIDs. Click Next. The Display Rule group box appears.From the Display Rule group box, you can do the following: • Select the Display Rule radio button. You can select either Everywhere or Near selected APs radio button. By default, Display everywhere is selected. If you select Display everywhere, then it searches for all the Mobile Concierge-supported controllers that provide these SSIDs and assigns these controllers to the MSE. If you select Display near selected APs, then you can configure the following parameters: AP—Select those APs on which you want the advertisements to broadcast. Radio—Select the radio frequency on which you want the advertisements to be broadcasted. The service advertisement is displayed when the mobile device is near the radio band that you have selected. The possible values are 2.4 GHz or 5 GHz. – min RSSI—Enter a value for RSSI at which you want the service advertisements to be displayed on the user interface. Click Finish.
  • Connected mobile experience

    1. 1. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1
    2. 2. Challenge Business and venue operators face increasing pressures from changing business landscape. © 2013 Cisco and/or its affiliates. All rights reserved. Challenge Business operators have very limited visibility into their business environment. Where, when and how do people move around the venue? Trend Explosion of Mobile Devices and BYOD connecting everyone, everywhere, all of the time. Trend WLAN networks becoming increasingly sophisticated enabling new capabilities and services Cisco Confidential 2
    3. 3. DETECT GUEST PRESENCE The customer’s personal mobile device and its characteristics are detected before they enter the venue. CONNECT GUEST ACCESS 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. ENGAGE GUEST EXPERIENCE The customer receives highly relevant content and services based on their preferences, profile, and real-time location within the business venue. LO CATI O N ANALYTI C S Customer: Presence in the venue. © 2013 Cisco and/or its affiliates. All rights reserved. IT: understand network utilization, peak usage, number and types of devices on the network. Business: insights into customer online and onsite behavior, most traffic paths, dwell times, location density etc. Cisco Confidential 3
    4. 4. RETAIL Consumers HOSPITALITY Guests • Context rich promotions • Maps with featured attractions • Informed purchase decisions • Happy hour show tickets • In-store experiences • Gift shop promotions © 2013 Cisco and/or its affiliates. All rights reserved. TRAVEL HEALTHCARE EDUCATION Passengers Patients Students • Staff security to passenger traffic flow • Wayfinding patient apps • Campus maps directions • Improved patient experiences • Stadium sales athletic event experience • Flight updates gate directions • Improve travel experiences • Medical device location history • Real-time bus maps Cisco Confidential 4
    5. 5. How does the vision map out to Solutions? DETECT ENGAGE CONNECT • Presence Detection • Auto On-Boarding • MSE Location Services • Hot Spot 2.0 • Location Analytics • Lobby Ambassador • ISE Mobile Concierge Concierge enables engaging with customers via different media On Device without Application 802.11u /MSAP (QC) Browser Mobile App (Future) Different ways to implement app Meridian App Editor © 2013 Cisco and/or its affiliates. All rights reserved. Mobile Concierge SDK Cisco Confidential 5
    6. 6. Advanced Location Services New Capabilities in 7.4 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6
    7. 7. • Overview • Licensing Changes & Software Requirements • Location Analytics (Think Smart Integration) • Mobile Concierge  App Based (Meridian Integration)  Device Based (Qualcomm Integration) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 7
    8. 8. Cisco Prime Infrastructure Management Station (Client Browser) Third Party Server SOAP/XML over HTTP/HTTPS Location API via SOAP/XML over HTTPS Wireless Clients © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 8
    9. 9. Platform Min SW versions Wireless LAN Controller Access Point 7.2 Cisco Prime Infrastructure 1.3 Mobility Services Engine © 2013 Cisco and/or its affiliates. All rights reserved. 7.2 7.4 Cisco Confidential 9
    10. 10. Location Analytics ThinkSmart Integration Transforming device positioning information into actionable Business Intelligence © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 10
    11. 11. • Overview • Enabling Analytics on the MSE • The Analysis Process • Reporting Interface • Verification & Troubleshooting Typical Issues © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 11
    12. 12. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 12
    13. 13. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 13
    14. 14. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 14
    15. 15. • 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. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 15
    16. 16. • 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= # © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 16
    17. 17. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 17
    18. 18. Report s MSE Location Analytics Architecture for Release 7.4 MSE Database Graphical User Interface Location Data Data Mediation Reporting Device/Path Database Results Database Thinksmart Analytics Engine WLC Location Data Mobility Services Engine © 2013 Cisco and/or its affiliates. All rights reserved. JBoss Application Server Automatic conversion of data to results on: dwell, device no., movement, frequency Cisco Confidential 18
    19. 19. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 19
    20. 20. • Open a WEB browser and navigate to http://<mse_IP_address>:8080/ui Default login is: Admin/Admin although any username configured on the MSE will work © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 20
    21. 21. • 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 Birds-eye or Overhead view Ideally the hardware would have a 3D graphics card to ensure compatibly with WebGL © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 21
    22. 22. • 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/an swer.py?hl=en&answer=1220892 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 22
    23. 23. • Analytics View with default building 3D Result Visualization Area Analysis Control Panel © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 23
    24. 24. • Two Dimensional Analytics View with Open Street Maps 2D Result Visualization Area Identical Analysis Control Panel © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 24
    25. 25. • 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. Switch between analysis and reporting Rule types to specify which devices are considered in the analysis Type of analysis to conduct Building to conduct the analysis on Start the analysis © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 25
    26. 26. • A number of rules together is called a ―rule set‖ — These can be saved and loaded to repeat the defined analysis criteria © 2013 Cisco and/or its affiliates. All rights reserved. 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 26 Cisco Confidential
    27. 27. • The panel in the upper right-hand corner provides navigation, view, and parameter selections Select 2D view or overhead perspective Select 3D view Point, Orbit, Pan and Zoom controls Additional Information Parameter Selection Result Visualization controls © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 27
    28. 28. • Analytics UI is reached at http://your.mse.ip.address:8080/ui © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 28
    29. 29. • q Selecting the Reporting button within the Analytics Visualization view takes you to the Report Generation view © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 29
    30. 30. • With this release of analytics processed on the MSE we are limited to five pre-canned report options © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 30
    31. 31. • Although reporting is limited to pre- designed formats, each report can still be customized to focus the output to a smaller data set. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 31
    32. 32. • Once a report is run the results are returned as a downloadable .pdf file © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 32
    33. 33. • 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) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 33
    34. 34. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 34
    35. 35. MSE 7.4 Wi-Fi Location Based Services Planning Guide Understanding Location Services Impact on Network Design Decisions © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 35
    36. 36. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 36
    37. 37. • Guidelines to provide deployment flexibility, more comprehensive planning E.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) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 37
    38. 38. • Wi-Fi AP measures and reports RSSI (Receive Signal Strength Indicator) to WLC OpenAPI (SOAP/XML) • WLC (unified/Flexconnect) Intra/ Internet aggregates and periodically reports them to MSE via NMSP Mobility Services Engine (MSE) w/ Mobile Concierge & Location Analytics • MSE applies advanced positioning NMSP algorithms • Determine location (RF fingerprinting/modeling) • Location notifications (e.g. to Meridian) • Cisco Prime Infrastructure SOAP/ XML LAN or WAN Statistical processing for Location Analytics • Cloud-based application (e.g. Meridian) Displaying all devices on a map in CPI Wireless LAN Controller unified or FlexConnect Wi-Fi Access Point (AP) Wi-Fi Client © 2013 Cisco and/or its affiliates. All rights reserved. Wi-Fi Access Point (AP) Wi-Fi Client Cisco Confidential 38
    39. 39. Co-located Partly Distributed Fully Distributed (AP, WLC & MSE in the same LAN) (AP on LAN, WLC & MSE remote) (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 MSE+WLC per data center (e.g. Retail HQ) MSE+WLC per site (e.g. Campus) Flexible MSE deployment options Internet (e.g. T-1) Internet (e.g. T-1) Intranet (e.g. OC-1) GigE LAN Cloud-based location application (e.g. Meridian) Cloud-based location application (e.g. Meridian) In-house/IT location application (e.g. corporate HQ) GigE LAN MSE per data center (e.g. Regional HQ) WAN/ Intranet (e.g. T-1) e.g. FlexConnect WLC e.g. Unified WLC Unified WLC per site (e.g. property/event) GigE LAN © 2010 Cisco and/or its affiliates. All rights reserved. WAN/ LAN GigE LAN Cisco Confidential 39
    40. 40. • Bandwidth considerations App Server — BW between MSE and Meridian servers — BW between WLC and MSE Meridian/ Cloud-based Location Server Considered in planning guide/calculator Not considered in planning guide/calculator — Transaction rate of MSE (Each location/zone based location update is a distinct SOAP/XML transaction) MSE compute cycles Monitoring & Routing • Computing cycle considerations Response from Meridian - Map data (images) - Current location (x,y, time) Core App Calls to Meridian - Get map Data - Get Current Location Sent to Meridian Cloud - Location Notifications - Map data SDK Client App Cisco MSE Cisco WLC © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 40
    41. 41. Use case Event Action Presence user enters building/store send welcome message form Mobile Concierge user is close to product display send advertisement Proximity Asset-tracking devices/tags has moved outside area alert loss prevention Mobility/path tracking Location Analytics updates Subject movements Zoned (Geo Fenced) Un-zoned RF Network supports such applications based on expected accuracy and currency. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 41
    42. 42. • 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 <2.5K Sq ft 15ft ~30s Mobility-tracking Mall, airport … © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 42
    43. 43. 5 – 7 meter CUWN with an average of 2500 – 5000 sq. ft cells © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 43
    44. 44. RF Uncertainty Movement error (currency) Client speed Uncertainty Estimation error (accuracy) uncertainty in exact RF propagation loss between the client and the AP Initial position estimation error uncertainty on speed of the user since the client device reports position periodically + Movement error TOTAL LOCATION ERROR © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 44
    45. 45. • 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. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 45
    46. 46. • 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. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 46
    47. 47. • 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) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 47
    48. 48. Location Analytics Application (LAA): co-located with MSE • LAA shares DB with MSE No additional BW needed between MSE & WLC • background task ran infrequently No 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) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 48
    49. 49. • 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 …) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 49
    50. 50. • 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) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 50
    51. 51. Samsung Tab (small) Samsung Tab (large) Samsung Phone Intel Phone Apple iOS Intel Laptop Generic (mix) Client Bandwidth Office Retail Access Point Controller Physical aspects Transactions Storage Currency Accuracy © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 51
    52. 52. Mobile Concierge – App Based Meridian Integration Engaging the customer © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 52
    53. 53. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 53
    54. 54. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 54
    55. 55. • Meridian is integrated into an existing WLAN by: Meridian — 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. © 2013 Cisco and/or its affiliates. All rights reserved. MS E WLC Push Notification — Meridian provides an online content management system to create placemarks, mobile app content and routing for turn-by-turn indoor navigation Get Location — 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 NMSP Cisco Confidential 55
    56. 56. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 56
    57. 57. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 57
    58. 58. • Enabling this integration will allow the MSE to send floor maps and wireless client position notification to Meridian ✓ © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 58
    59. 59. 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 59
    60. 60. • 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 process Link to download the iOS or Android SDK Information on which Campus, Building and Floor information that has been transmitted to the Meridian servers © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 60
    61. 61. • Follow the emailed activation link to create your login credentials Note - Meridian currently only supports the Chrome and Safari browsers for accessing their Website © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 61
    62. 62. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 62
    63. 63. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 63
    64. 64. View the Clients known to your MSE in real time and watch them update as their positions change 2 1 3 Upgrade your account to receive a 60 day free trial of the Editor features © 2013 Cisco and/or its affiliates. All rights reserved. 4 Cisco Confidential 64
    65. 65. 3 2 1 4 5 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 65
    66. 66. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 66
    67. 67. I. 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 support@meridianapps.com © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 67
    68. 68. Mobile Concierge – Device Based Qualcomm Partnership © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 68
    69. 69. • 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) © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 69
    70. 70. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 70
    71. 71. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 71
    72. 72. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 72
    73. 73. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 73
    74. 74. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 74
    75. 75. • 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 Used to configure the validity timeframe for the assistance data before requiring refresh © 2013 Cisco and/or its affiliates. All rights reserved. SSID returned to mobile device by PDS server for MSAP attachment Cisco Confidential 75
    76. 76. • 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 1 Embedded MSAP client tries to detect support for MSAP using the beacons coming from the APs Qualcomm based mobile device enters the venue DNS Services 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 Wireless LAN Controller 4 3 Mobility Services Engine © 2013 Cisco and/or its affiliates. All rights reserved. 2 Once the MSE hostname is resolved the MSAP client on the phone communicates with the MSAP service to fetch all available Service Advertisements Cisco Confidential 76
    77. 77. • 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 • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 77
    78. 78. • The Mobile Concierge Venue defines the boundaries for advertised services © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 78
    79. 79. • 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 Icon files must be ≥ 8Kb with 4Kb or less preferred Defines the loyalty App recommended for the venue Defines the OS the defined URI is intended to operate on Identifies App location – On the Device or on the WEB © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 79
    80. 80. • 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 © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 80
    81. 81. Cisco 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 Web http://iwe.cisco.com/ws#web/view-post/post/-/posts?postId=340700223 For any inquiry – sell_mobile_experiences@cisco.com © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 81

    ×